>From the 4.0.0 release notes:
http://sourceforge.net/docman/display_doc.php?docid=24779&group_id=22866
The 4.0.0 release ships with a different set of pre-configured server
configuration file sets:
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. Note that this can cause migration difficulties when porting
from a 3.2.x release which was not using scoped class loading. Try the standard
configuration if you see class loading issues during migration.
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.
We are reverting back to the 3.2.x default configuration file sets for the
4.0.1 release since this has caused so many issues.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3856930#3856930
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3856930
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
