I am running up against this issue as well. Did you determine if this is the only workaround for jboss 4.0.3?
With classloader logging and JMX inspection, I can see that it will load a dom4j jar stashed in the WAR (only, however, if it appears in the manifest class-path). However it seems to stubbornly insist on using the dom4j classes from the NoAttributeClassLoader (that is, the bootstrap one). Very annoying. You would NEVER want to package a jar inside an application only to have it superseded by one in the app server... -m View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941107#3941107 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3941107 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
