Right now its only in "default" and "all" in order to not overly
increase the size of the JBAS distribution. [The console is around 10mb in size, mostly
Seam and richfaces].
It may be possible to include it in other configs out of the box if a reasonable jar
sharing scheme is implemented, however right now its up to the user to copy the console to
other configs. One other reason that its not in "web" is that we've not
tested it in that config.
There is no reason I can think of off the top of my head why the console shouldn't run
in the "web" profile, since it doesnt utilize EJBs. If you can run regular Seam
apps, the console should be fine, if you try it and hit problems please raise a jira in
https://jira.jboss.org/jira/browse/EMBJOPR
Thanks
Charles
----- "Jaikiran Pai" <jpai(a)redhat.com> wrote:
Any specific reason, we want to limit it to "default" and
"all"? By
the
way, does the admin-console functionality in AS5 rely on the server
configuration having EJB support? I was thinking whether end users can
use the admin-console within a "web" server configuration (which does
not have EJB support).
-Jaikiran
Dimitris Andreadis wrote:
> As it is now it's in 'standard', 'default', 'all'.
>
> I'd thought we would only include it in 'default' and 'all' ?
>
> /D
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development