you already has one inside the TOMCAT_HOME%/lib/container .. the files
jaxp.jar + parser.jar...copy this files to your apps web-inf/lib dir...
or use xerces < http://xml.apache.org/xerces-j/index.html >
Saludos ,
Ignacio J. Ortega
> -----Mensaje original-----
> De: Claudia Pietsch [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 31 de mayo de 2001 0:27
> Para: [EMAIL PROTECTED]
> Asunto: RE: struts in tomcat 3.3-m3
>
>
> Where I can get this Parser?
>
> Claudia
>
>
> At 23:43 30.05.2001 +0200, you wrote:
> >Tomcat 3.3 does not put anything on the webapp's classpath....in
> >particular prior Tomcat 3.3 there was a XMLParser in the classpath of
> >the executed webapps..
> >
> >To solve this issue you need to put a XMLparser in the
> classpath of your
> >webapp there are to 2 ways to achieve that..
> >
> >* in the WEB-ibf/lib dir of you webapp, the standard way, or
> >* in the %TOMCAT_HOME%/lib/apps dir..
> >
> >Hope that helps
> >
> >Saludos ,
> >Ignacio J. Ortega
> >
> >-----Mensaje original-----
> >De: Steve Salkin [mailto:[EMAIL PROTECTED]]
> >Enviado el: mi�rcoles 30 de mayo de 2001 22:15
> >Para: '[EMAIL PROTECTED]'
> >Asunto: struts in tomcat 3.3-m3
> >
> >
> >Hi-
> >Has anyone (else) had trouble deploying a struts application on
> >tomcat-3.3-m3 that works fine under 3.2.2? I (and several
> people here)
> >are experiencing oddness when trying to do this. It doesn't
> seem to be
> >particular to our app either, since the struts-example.war
> also causes
> >tomcat to fail during start-up.
> >The error is a basically a failure to create a SaxParser from the
> >SaxParserFactory - this is a static method that looks for a specific
> >concrete class, either from a system property or an
> >implementation-defined default. Apparently this is not occuring.
> >Workarounds would be welcome: the tag-pooling feature of 3.3
> has a lot
> >of promise for a struts app.
> >Thanks,
> >Steve Salkin
>
>
