Another way ( easy way at least ) is to get Tomcat 3.3 Beta 1 and use
it..
It implaments too a isolated classloader schema for webapps and
internals..
Saludos ,
Ignacio J. Ortega
> -----Mensaje original-----
> De: Andrew Cooke [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 31 de julio de 2001 15:42
> Para: [EMAIL PROTECTED]
> Asunto: SAX 2.0, sealing, Tomcat 3.2.3
>
>
>
> Hi,
>
> I've spent most of the day reading through various mailing list
> entries and other pages on the net and am still confused. Is there a
> FAQ anywhere that clearly summarizes the issues involved and answers
> the questions below? If not, can someone please tell me:
>
> - Should Tomcat 3.2.3 work with JSP pages that use JAXP 1.1 and
> crimson (the XML support from Sun)?
>
> - If so, how do I get it to work?
> -- Someone here says that it depends on the order of jars in the
> classpath. Doesn't seem to make any difference to me - any comments?
> -- I have managed to get past the sealed jar problems by unsealing
> jars, but then get an error suggesting that the code in Tomcat is SAX
> 1.0 (getXmlReader in org.xml.sax.XMLReader doesn't appear to exist,
> which is a SAX 2.0 method?).
>
> - If not, what other choices do I have?
> -- Will Tomcat 4.0 work?
> -- Will Tomcat 4.0 still give errors with sealed jars? Is there a
> work-round?
>
> In particular, our code gives the "usual" sealed jar exception unless
> I unseal our copy of xalan.jar, at which point I get a NoSuchMethod
> call when executing
> SAXParserFactory factory = SAXParserFactory.newInstance()
> in our code.
>
> Thanks,
> Andrew
>
>
