Re: Problem faced when both xerces.jar and servlet.jar are in Cla sspath

[Faizy . Chaudhary]

I faced the similar problem. The probable solution to your problem is   1.firstly, replace your servlet.jar with the latest one.       OR, if the problem still persists   2.If you do not have j2ee.jar, download version 1.3 from the internet and keep it in the classpath.   This error is thrown because JVM gets the older version of the class, which does not have all the methods defined. j2ee.jar version 1.3 contains latest classes of j2ee with all the methods.   regards faizy [Faizy Chaudhary-PU]  -----Original Message----- From: Seema Kumar [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 10:13 AM To: [EMAIL PROTECTED] Subject: Problem faced when both xerces.jar and servlet.jar are in Classpath Hi all,   I am facing a problem when both servlet.jar and xerces.jar are present together in my classpath. The problem being while parsing an XML file using the xerces parser, the jvm throws a noSuchMethod exception for a the DOM class.   This problem was worked around by adding xerces at the beginning of the classpath, before servlet.jar. However, when this is done for a web based application, tomcat by default includes all the .jar files in the lib directory in alphabetical order, wherein, servlet.jar comes in before xerces.jar and the parsing fails. I found a temporary workaround by renaming xerces.jar to a_xerces.jar. But could somebody suggest a more sensible solutiong to this problem ?   Thanks in advance Seema ---------------------------------------------------------------------------- This message contains privileged and confidential information and is intended only for the individual named. If you are not the intended recepient you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and immediately delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. --------------------------------------------------------------------------