Hi,
I have a legacy EAR which is currently deployed on JBoss 3.0.8. This contains a WAR
an EJB JAR, and the web app invokes an EJB in the EJB JAR. This has always worked fine
using the UCL and with Jetty's Java2ClassLoadingCompliance set to true.
However, I now need to deploy a new EAR
All,
I need to upgrade me to 3.2.2 to get some of the primary key gen fixes in
that version. I had hoped that the upgrade would be fairly transparent as
it's only a minor release. However now my app fails to deploy. I believe
this is due to some of the Class Loader changes that went into 3.2.1
Show the full deployment output to see if there are any manifest entry
warnings. Also run the attached ListJar program passing in the path to
the deployment to illustrate the archive structure.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Classloader Issues with EAR files
Hello,
I have a servlet that loads a resource bundle. When I deploy the WAR file
that
contains the servlet, the resource bundle is discovered and loaded by the
following statement:
bundle
I have a servlet that loads a resource bundle. When I deploy the WAR file that
contains the servlet, the resource bundle is discovered and loaded by the
following statement:
bundle = ResourceBundle.getBundle(bundleName);
When I deploy the WAR file as part of an EAR file, the classloader
