This content has been marked as final.
Show 2 replies
-
1. Re: Deployment isolation problem with ear being ported from
jaikiran Sep 17, 2009 10:27 AM (in response to jwchristy)Try packaging the application like this:
myapp.ear | | |--- META-INF | |--- application.xml | |--- jboss-app.xml | | |--- lib [This will contain jar files which are to be available to all components in the EAR] | | --- xyz.jar (plain jar files) | | --- more plain jar files | | |--- ejbjar1.jar | |--- ejbjar2.jar | |--- myapp.war | |---
If that still does not work, then provide more details about the exact issue. -
2. Re: Deployment isolation problem with ear being ported from
jwchristy Sep 17, 2009 5:34 PM (in response to jwchristy)I initially moved all the non-EJB jars into a lib directory, and then the app's Spring initialization starting failing. A different component had a dependency on having its jars at the top level of the ear.
After identifying those jars (and making a note to go back and find the configuration that created that dependency!), and leaving them at the top level of the ear with all of the rest of the jars in a lib directory, the app finally worked, with the old JAXB.
Thanks jaikiran, you are awesome. This issue has been holding me up for some time - where do I send the case of {insert your favorite beverage here}? :-)