It was my patch that changed this. I changed the EARDeployer to only deploy those applications listed in an application.xml file (I believe that this was another bug on sourceforge?). The struts.jar should only be included on the classpath if it is an application in the application.xml file, if it is in the WEB-INF/lib, or if it is listed in a Class-Path entry in the META-INF file. I believe this is how the spec defines things. Is this right?
-Larry > Bugs item #544848, was opened at 2002-04-16 15:19 > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=376685&aid=544848&group_id= 22866 > > Category: None > Group: v3.0 Rabbit Hole > Status: Open > Resolution: None > Priority: 5 > Submitted By: Peter Luttrell (objec) > Assigned to: Nobody/Anonymous (nobody) > Summary: EAR Deployments don't work the same > > Initial Comment: > with jboss3.0rc1 with tomcat4.0.3 if I create an ear > file such as this: > > one.war > two.war > struts.jar > META-INF/application.xml > > where one.war and two.war depend on structs.jar, jboss > blows up when one.war attempts to preload the structs > servlet. > > with jboss3.0b1 with tomcat4.0.3, the above > configuration worked perfectly. > > was this intentionally changed? or is it a bug? > > if i use the "Class-Path" entry to specify the > structs.jar file in the manifest file for both one.war > and two.war it also works. I've only tested this on > rc1. > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=376685&aid=544848&group_id= 22866 > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
