The configurations found in this dist include:
default: The default configuration with all required j2ee 1.4 services. It
also uses
scoped deployments for ears with call by value semantics for ejb calls, and
jndi lookups.
standard: The configuration consistent with the legacy 3.2.x 'default'
configuration
that uses unscoped deployments and call by reference semantics for same VM ejb
calls
and jndi lookups.
minimal: A minimal configuration with hot deployment of services, and a
logging and jndi
naming service.
all: The all inclusive configuration of the services avaliable in jboss.
I'm not seeing the indicated exception but I'll need to check all the binaries in
case one was not updated on sourceforge correctly. Its actually a harmless exception
that shows up in the configurations which do not include the aop classes.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848996#3848996
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848996
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
