>
> One thing related to this but not to Tomcat 3.3. I'm using
> Xerces and Xalan
> and I have to place the Xerces and Xalan jars in the
> tomcat.sh/bat classpath
> because Xerces has newer org.w3c.dom stuff in it. The old
> Tomcat 3.2.1 XML
> stuff (w3c.jar) misses some methods and stuff...
>
No need to do that way, in 3.3 or 4.0 ..., the container classloader is
independent of the webapps classloader ( they are siblings FYI ), you
only need to deploy a war file and everything goes ok...
> That's somehow kind of fucked. Does anyone have a solution
> for this or does
> it get any better in 3.3????
See comment above, no need to change 3.3 classpath to run an app that
uses another xml parser from a war file...
>
>
> Then the last problem. I tried to use Cocoon under tomcat 4b
> and it wouldn't
> work because of a sealing violation... Known to u guys???
>
I think Craig has done it in CVS , pick a nightly build or from CVS,
hopefully it will be solved.., basically the problem has been solved by
creating another classloader layer for Jasper xml parser needs..
Saludos ,
Ignacio J. Ortega
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
