This content has been marked as final.
Show 5 replies
-
1. Re: Class loader isolation broken in 4.2.0GA
apill Jul 18, 2007 9:12 AM (in response to apill)Is this related to http://jira.jboss.org/jira/browse/JBAS-4536 ?
-
2. Re: Class loader isolation broken in 4.2.0GA
dimitris Jul 18, 2007 4:19 PM (in response to apill)The warning is pretty straightforward. Only a root deployment can define a new classloading scope/domain.
I don't recall what was the exact fix we made, but it seems your packaging could be wrong before. -
3. Re: Class loader isolation broken in 4.2.0GA
apill Jul 19, 2007 3:53 AM (in response to apill)Where should the file be packaged? At the moment it is in the ear inside META-INF/jboss-app.xml
Please can you tell me where I should move it to. -
4. Re: Class loader isolation broken in 4.2.0GA
apill Jul 19, 2007 3:55 AM (in response to apill)http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration seems to suggest it should me inside the META-INF directory.
-
5. Re: Class loader isolation broken in 4.2.0GA
apill Jul 19, 2007 5:53 AM (in response to apill)Fixed the problem. In jboss-service.xml
<attribute name="URLs"> deploy/,mydeploy </attribute>
Needed to be<attribute name="URLs"> deploy/,mydeploy/ </attribute>
Bummer! Not an easily found. The app server was deploying mydeploy dir as the root because I forgot the slash!