I originally posted this over on the Jetty list, and they suggested I cross-post to get you guys in the loop.
I downloaded and checked out JBoss3.2.0 beta yesterday. I'm on MacOS X 10.2 / Apple's 1.3.1_03 JVM. I deployed 2 ears. Both ears work fine on 3.02. ** ALL EARS ARE DEPLOYED IN THEIR OWN CLASSLOADERS USING THE jboss-app.xml FILE TAGS ** This is because I deploy a similar content management system in different EARs and without this, they classes were conflicting... Anyway, it works great in 3.02. The first ear to deploy worked without problems. It contained one WAR and one JAR w/EJBs. The WAR contained a JAR with some classes in it used by servlets. Worked fine. The second ear to deploy contained two WARs and one JAR w/EJBs. Both WARs had similar structure. One worked fine, the other would act as if the stuff in its WEB-INF/lib directory were not added to the JSP compiler classpath. It would complain that included classes in the JSPs did not exist. I verified that they did exist by exploding the archive. Also, the same EAR functioned correctly on 3.02. Anyway, if anyone has any clues or would like some more information let me know. Hunter ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
