> At 02:42 PM 7/31/01 +0100, you wrote: > [...] >>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() > > Grrr. Wrong line. The error comes from: > > myParser = factory.newSAXParser().getXMLReader(); > > Sorry, > Andrew De todos modos, con Tomcat 4.0 ya no tendrias ese inconveniente. Puedes usar varios parsers factories (uno en cada contexto) pues mantiene un classloader diferente por contexto. Suerte!!! Good luck! Bernardo
- SAX 2.0, sealing, Tomcat 3.2.3 Andrew Cooke
- Re: SAX 2.0, sealing, Tomcat 3.2.3 Andrew Cooke
- RE: SAX 2.0, sealing, Tomcat 3.2.3 BERNARDO ANTONIO BUFFA
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Loïc Lefèvre
- Re: SAX 2.0, sealing, Tomcat 3.2.3 Andrew Cooke
- Re: SAX 2.0, sealing, Tomcat 3.2.3 Pier P. Fumagalli
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Andrew Inggs
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Andrew Cooke
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Ignacio J. Ortega
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Andrew Inggs
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Andrew Cooke
- RE: SAX 2.0, sealing, Tomcat 3.2.3 Bryan Rood
- Tomcat 4.0 stability (Was: Re: SAX 2.0, se... Pier P. Fumagalli