If you are using Tomcat 3.2 or later, then it uses JAXP. You can remove jaxp.jar and parser.jar from the lib directory in Tomcat and replace them with xerces.jar quite safely (according to developers of Tomcat)
Pete > ---------- > From: Ren� Jensen[SMTP:[EMAIL PROTECTED] > Sent: 26 February 2001 15:27 > To: [EMAIL PROTECTED] > Subject: RE: using xerces 1.3.0 with servlets > > Citat Keith Jensen <[EMAIL PROTECTED]>: > > > > > Rene, > > > > Try moving xerces.jar around in your classpath > > and see what happens. Try putting it before any > > jars, zips, etc that you added when doing the > > servlet version. If this changes the behavior > > then there must be something in the other jars > > that contains an old xerces version of the > > org.apache.xerces.parsers.DOMParser class that > > does not implement the startElement method. > > > > Regards, > > > > Keith > > > > > > OK... this _was_ (kind of) the problem. > > TomCat uses xml for it�s configuration, and therefore it implements a > parser > (some parser from SUN). > When starting, TomCat runs a script that prepends some jarfiles to your > classpath, apparently one of these jar-files contains an implementation af > > DOMParser, that dosn�t implement the startElement method. > > the workaround is to fix the startupscript so that the extra jarfiles is > appended to the original classpath insted of prepended. > > (I know this could mess up TomCat. It could be this isn�t the only method > thats > dublicated in the two jar-files. But Tomcat hasn�t chrashed on me .. yet) > > Thanks a lot for the help. > > _\|/_ > (@ @) > ---oOOo-(_)-oOOo--- > Ren� Jensen > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
