-
1. Re: 8.0.0 to 8.1.0 migration class loading issue
jason.greene Jun 2, 2014 6:33 PM (in response to mandrosen)Do you have any specialized class loading configuration?
Could you share jboss-deployment-structure.xml, application.xml, and any manifest.mf files that contain classpath, extensions, or module imports?
-
2. Re: Re: 8.0.0 to 8.1.0 migration class loading issue
mandrosen Jun 2, 2014 6:42 PM (in response to jason.greene)Absolutely.
-
application.xml 574 bytes
-
jboss-deployment-structure.xml 285 bytes
-
webapp.MANIFEST.MF 302 bytes
-
-
3. Re: Re: Re: 8.0.0 to 8.1.0 migration class loading issue
jason.greene Jun 2, 2014 6:51 PM (in response to mandrosen)Thanks.
Ok so the behavior change is caused by a bug in 8.0.0 that prevented sub deployment isolation from getting honored, which now works correctly in 8.1:
<ear-subdeployments-isolated>true</ear-subdeployments-isolated>
I also notice that your web app has an empty Class-Path, so these two combined lead to your war not being able to see classes in your ejb jar. So you can either add a Class-path reference in your war's META-INF/Manifest.MF to point to your ejb jar. Or you could remove that isolation flag (or set it to false).
Let me know if that works for you.
Thanks!
-
4. Re: Re: Re: Re: 8.0.0 to 8.1.0 migration class loading issue
jason.greene Jun 2, 2014 6:53 PM (in response to jason.greene)BTW If you go the Class-Path route it would look like this:
Class-Path: app.jar
-
5. Re: 8.0.0 to 8.1.0 migration class loading issue
mandrosen Jun 3, 2014 11:46 AM (in response to mandrosen)Thank you. I just needed the to set isolated to false. It works with and without the Class-Path set.