I posted this exact bug along with a simple fix last week, but was told by Scott Stark that he was going to "rip all that out" because the JBoss unified classloader should not be handling classes within a WAR file.
By the way, deploying a plain WAR file (not within an EAR), like for example the struts-example.war that comes with Struts, does not work either. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jan Bartel Sent: Wednesday, February 20, 2002 2:40 AM To: marc fleury Cc: Jules Gosnell; Greg Wilkins; [EMAIL PROTECTED] Subject: [JBoss-dev] ClassLoader problems with war contents Marc, The Jetty/JBoss integration is still using a MortBay classloader to load the contents of war files as the JBoss MBeanClassLoader does not appear to return us classes from the WEB-INF/classes directory. I think this could be due to the part of the package name becoming appended onto the URL for xxx/WEB-INF/classes. Eg when running the servlets in jbosstest-web.ear, we see: Servlet ClassLoader[2]: org.jboss.system.MBeanClassLoader:935439853 URLs: [25] = file:/home/janb/new-jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/66 .jbosstest-web.war.webinf/WEB-INF/classes/org/jboss/test/web/servlets/ We will stop using the MortBay classloader if we can get the MBeanClassLoader to supply all jars and /classes/* from a war. cheers, Jan _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
