Indeed it shouldn't, but for some reason whilst loading the configuration from WEB-INF, JBoss/Tomcat decides to use the Digester class loaded using the system class loader and not the web app's class loader. I walked through the deployment code and the class loader for the Digester is null. My class loader knowledge isn't great but I assume this means the system class loader.
The fact that it works for James Mitchell, suggests there is probably something really obvious wrong with my set-up, but I can't see it. -----Original Message----- From: Eddie Bush [mailto:[EMAIL PROTECTED]] Sent: 09 October 2002 22:52 To: Struts Users Mailing List Subject: Re: JBoss-3.0.3_Tomcat4_1_12 It shouldn't matter. That shouldn't even have a chance to affect a web-app -- that's in the server's private classloader path. Theo Harper wrote: >Do you have common-digester in >jboss-3.0.3_tomcat-4.1.12/tomcat-4.1.x/server/lib/commons-digester.jar? > -- Eddie Bush -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
