The new 'web' profile is going to be included anyway at some point, so the sooner
the
better, I guess.
Also, I'm waiting for things to stabilize in trunk to introduce the 'standard'
profile.
Maybe with this newer more lightweight web-profile we could change the 'default'
one to have
the 'standard' settings, rather than introducing yet another one. This more or
less means
adding iiop, call-by-value and classloading isolation.
I'm not yet clear what is the best choice.
Adrian Brock wrote:
WRT:
https://jira.jboss.org/jira/browse/JBAS-5897
I'd like to include the "web profile"
in the open source distribution.
We would document this as "experimental", i.e.
the configuration is likely to change before
it is stabilised.
That's because it is not quite finished yet,
there's still issues with making jta/jca optional,
factoring out the jpa deployer from ejb3 and
the http invoker currently required to make
shutdown.sh work.
Including the web profile easier now we have the shared libraries
since it won't increase the size of the
distribution anything like as much as before.
I propose that you should be able to start it using:
./run.sh -c web
The web profile currently looks like this:
deployers:
alias-deployers-jboss-beans.xml
ejb3.deployer
jboss-aop-jboss5.deployer
jboss-jca.deployer
jbossweb.deployer
metadata-deployer-jboss-beans.xml
security-deployer-jboss-beans.xml
deploy:
hsqldb-ds.xml
http-invoker.sar
jboss-local-jdbc.rar
jbossweb.sar
jboss-xa-jdbc.rar
jca-jboss-beans.xml
jmx-console.war
jmx-invoker-service.xml
ROOT.war
security
transaction-jboss-beans.xml