Much more simply: try Tomcat 3.3 and up, they solve almost all
classloader issues as yours..
Saludos ,
Ignacio J. Ortega
> -----Mensaje original-----
> De: Douglas Smith [mailto:[EMAIL PROTECTED]]
> Enviado el: lunes 26 de marzo de 2001 3:50
> Para: [EMAIL PROTECTED]
> Asunto: Overiding Tomcat's CLASSPATH
>
>
> Hello all,
>
> I'm having a problem in that Tomcat is loading deprecated XML DOM
> interfaces located in Tomcat's lib/parser.jar instead of the DOM Level
> 2 interfaces in xerces.jar, which I'm distributing in my WEB-INF/lib
> folder inside a .war file.
>
> To get around this I can remove parser.jar but I'd like my app to work
> as a drop in war deployment.
>
> I suppose I could try to write a custom class loader, but this seems
> drastic.
>
> Does anyone have any ideas?
>
> [Wouldn't it make sense for Tomcat to ensure that each webapp had it's
> own classpath and that the classes distributed with the app had
> preference???]
>
> Thank you very much,
>
> Douglas Smith
> [EMAIL PROTECTED]
>
>
> -
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
>
