> The problem is with the DOM level used by the different xml packages.
> Tomcat 3.x exposes the interfaces in its xml package to all
Tomcat 3.� does not suffer this problem....it has a classloading scheme
where webapps obtain a clean classloader with only servlet.jar in it..
So is not 3.X is tomcat 3.2.x and down :)..
Saludos ,
Ignacio J. Ortega
Saludos ,
Ignacio J. Ortega
> the webapps. No
> amount of juggling classpath will change this--whatever
> Tomcat uses for
> reading the config files, must also be tolerated by every
> webapp. DOM1 DOM2
> is big problem. Other nasties like W3C interface changes can
> make life
> miserable.
>
> This is a pain in the ass royale with the v3 classloader scheme.
>
> If you want Xalan/Xerces, try to replace the JAXP package
> used by tomcat
> (crimson?) and all your webapps can use that package.
>
> Tomcat 4 does not impose its dependencies upon webapps. You
> just put what
> you need for each webapp in their own libs. ahh
>
> Jim
>
>
Saludos ,
Ignacio J. Ortega
