Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
Betty- The problem is with the order the jars are loaded. There is a version confilict with some classes. A common workaround is to rename parser.jar into zparser.jar, so it is loaded after xalan.jar and xerces.jar. This worked for me. -markus - Original Message - From: Betty Chang To: [EMAIL PROTECTED] Sent: Wednesday, July 04, 2001 5:34 AM Subject: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Hi -- I'm running a servlet application that uses the apache-XML xalan.jar and xerces.jar files for handling XML/XSL stuff. With tomcat 3.2.1, when I run my servlet, I get NoSuchMethodError on getNamespaceURI(), called by org.apache.xpath.DOM2Helper.getNamespaceOfNode(). I solved this problem by removing the jaxp.jar and parser.jar files that come with the tomcat installation and sit under the lib directory. The servlet still runs without those jar files, so the xalan.jar and xerces.jar must do the trick. Is there some kind of version conflict that causes the NoSuchMethodError? Thanks Betty
RE: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
Markus Are you suggesting that the jars are loaded in alphabetical order? I would have said you should either move parser.jar to the end of the class path or remove it entirely since xerces.jar contains the necessary jaxp interfaces. Tomcat 3.2 does not access the parser directly but through jaxp so you can safely remove parser.jar and jaxp.jar and use only xerces.jar. Pete -Original Message-From: Markus Strickler [mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 08:57To: [EMAIL PROTECTED]Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Betty- The problem is with the order the jars are loaded. There is a version confilict with some classes. A common workaround is to rename parser.jar into zparser.jar, so it is loaded after xalan.jar and xerces.jar. This worked for me. -markus - Original Message - From: Betty Chang To: [EMAIL PROTECTED] Sent: Wednesday, July 04, 2001 5:34 AM Subject: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Hi -- I'm running a servlet application that uses the apache-XML xalan.jar and xerces.jar files for handling XML/XSL stuff. With tomcat 3.2.1, when I run my servlet, I get NoSuchMethodError on getNamespaceURI(), called by org.apache.xpath.DOM2Helper.getNamespaceOfNode(). I solved this problem by removing the jaxp.jar and parser.jar files that come with the tomcat installation and sit under the lib directory. The servlet still runs without those jar files, so the xalan.jar and xerces.jar must do the trick. Is there some kind of version conflict that causes the NoSuchMethodError? Thanks Betty
Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
JAXP shipped with tc3 is 1.0. If this jar gets on the classpath before xerces then it won't work. Either removing jaxp or updating it to 1.1 will solve the problem. Antony Markus Are you suggesting that the jars are loaded in alphabetical order? I would have said you should either move parser.jar to the end of the class path or remove it entirely since xerces.jar contains the necessary jaxp interfaces. Tomcat 3.2 does not access the parser directly but through jaxp so you can safely remove parser.jar and jaxp.jar and use only xerces.jar. Pete -Original Message- From: Markus Strickler [mailto:[EMAIL PROTECTED]] Sent: 04 July 2001 08:57 To: [EMAIL PROTECTED] Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Betty- The problem is with the order the jars are loaded. There is a version confilict with some classes. A common workaround is to rename parser.jar into zparser.jar, so it is loaded after xalan.jar and xerces.jar. This worked for me. -markus - Original Message - From: Betty Chang mailto:[EMAIL PROTECTED] To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2001 5:34 AM Subject: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Hi -- I'm running a servlet application that uses the apache-XML xalan.jar and xerces.jar files for handling XML/XSL stuff. With tomcat 3.2.1, when I run my servlet, I get NoSuchMethodError on getNamespaceURI(), called by org.apache.xpath.DOM2Helper.getNamespaceOfNode(). I solved this problem by removing the jaxp.jar and parser.jar files that come with the tomcat installation and sit under the lib directory. The servlet still runs without those jar files, so the xalan.jar and xerces.jar must do the trick. Is there some kind of version conflict that causes the NoSuchMethodError? Thanks Betty
Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
Pete- AFAK the Startscripts for tomcat construct their own classpath from the lib directory during startup. This is done in alphabetical order, on most platforms. So renaming parser.jar is a quick and dirty way to move it to the end of the Tomcat classpath. See http://xml.apache.org/cocoon/install.html#tomcatfor details. -markus - Original Message - From: Edwards, Peter To: '[EMAIL PROTECTED]' Sent: Wednesday, July 04, 2001 10:14 AM Subject: RE: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Markus Are you suggesting that the jars are loaded in alphabetical order? I would have said you should either move parser.jar to the end of the class path or remove it entirely since xerces.jar contains the necessary jaxp interfaces. Tomcat 3.2 does not access the parser directly but through jaxp so you can safely remove parser.jar and jaxp.jar and use only xerces.jar. Pete -Original Message-From: Markus Strickler [mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 08:57To: [EMAIL PROTECTED]Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Betty- The problem is with the order the jars are loaded. There is a version confilict with some classes. A common workaround is to rename parser.jar into zparser.jar, so it is loaded after xalan.jar and xerces.jar. This worked for me. -markus - Original Message - From: Betty Chang To: [EMAIL PROTECTED] Sent: Wednesday, July 04, 2001 5:34 AM Subject: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Hi -- I'm running a servlet application that uses the apache-XML xalan.jar and xerces.jar files for handling XML/XSL stuff. With tomcat 3.2.1, when I run my servlet, I get NoSuchMethodError on getNamespaceURI(), called by org.apache.xpath.DOM2Helper.getNamespaceOfNode(). I solved this problem by removing the jaxp.jar and parser.jar files that come with the tomcat installation and sit under the lib directory. The servlet still runs without those jar files, so the xalan.jar and xerces.jar must do the trick. Is there some kind of version conflict that causes the NoSuchMethodError? Thanks Betty
RE: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
Markus You are right, I had forgotten that the scripts (even on NT) now create the class path dynamically. I was thinking of situations where I'm debugging in JBuilder and the classpath is static. I still suggest that it's as easy to make Tomcat use xerces instead of jaxp and parser - are you aware of any issues with this? Pete -Original Message-From: Markus Strickler [mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 09:43To: [EMAIL PROTECTED]Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Pete- AFAK the Startscripts for tomcat construct their own classpath from the lib directory during startup. This is done in alphabetical order, on most platforms. So renaming parser.jar is a quick and dirty way to move it to the end of the Tomcat classpath. See http://xml.apache.org/cocoon/install.html#tomcatfor details. -markus - Original Message - From: Edwards, Peter To: '[EMAIL PROTECTED]' Sent: Wednesday, July 04, 2001 10:14 AM Subject: RE: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Markus Are you suggesting that the jars are loaded in alphabetical order? I would have said you should either move parser.jar to the end of the class path or remove it entirely since xerces.jar contains the necessary jaxp interfaces. Tomcat 3.2 does not access the parser directly but through jaxp so you can safely remove parser.jar and jaxp.jar and use only xerces.jar. Pete -Original Message-From: Markus Strickler [mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 08:57To: [EMAIL PROTECTED]Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Betty- The problem is with the order the jars are loaded. There is a version confilict with some classes. A common workaround is to rename parser.jar into zparser.jar, so it is loaded after xalan.jar and xerces.jar. This worked for me. -markus - Original Message - From: Betty Chang To: [EMAIL PROTECTED] Sent: Wednesday, July 04, 2001 5:34 AM Subject: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Hi -- I'm running a servlet application that uses the apache-XML xalan.jar and xerces.jar files for handling XML/XSL stuff. With tomcat 3.2.1, when I run my servlet, I get NoSuchMethodError on getNamespaceURI(), called by org.apache.xpath.DOM2Helper.getNamespaceOfNode(). I solved this problem by removing the jaxp.jar and parser.jar files that come with the tomcat installation and sit under the lib directory. The servlet still runs without those jar files, so the xalan.jar and xerces.jar must do the trick. Is there some kind of version conflict that causes the NoSuchMethodError? Thanks Betty
Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
Pete- I'm not aware of any issues with your solution, but I never tried it either, as the workaround with renaming the jars gave me the results I wanted. -markus - Original Message - From: Edwards, Peter To: '[EMAIL PROTECTED]' Sent: Wednesday, July 04, 2001 11:16 AM Subject: RE: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Markus You are right, I had forgotten that the scripts (even on NT) now create the class path dynamically. I was thinking of situations where I'm debugging in JBuilder and the classpath is static. I still suggest that it's as easy to make Tomcat use xerces instead of jaxp and parser - are you aware of any issues with this? Pete -Original Message-From: Markus Strickler [mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 09:43To: [EMAIL PROTECTED]Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Pete- AFAK the Startscripts for tomcat construct their own classpath from the lib directory during startup. This is done in alphabetical order, on most platforms. So renaming parser.jar is a quick and dirty way to move it to the end of the Tomcat classpath. See http://xml.apache.org/cocoon/install.html#tomcatfor details. -markus - Original Message - From: Edwards, Peter To: '[EMAIL PROTECTED]' Sent: Wednesday, July 04, 2001 10:14 AM Subject: RE: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Markus Are you suggesting that the jars are loaded in alphabetical order? I would have said you should either move parser.jar to the end of the class path or remove it entirely since xerces.jar contains the necessary jaxp interfaces. Tomcat 3.2 does not access the parser directly but through jaxp so you can safely remove parser.jar and jaxp.jar and use only xerces.jar. Pete -Original Message-From: Markus Strickler [mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 08:57To: [EMAIL PROTECTED]Subject: Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Betty- The problem is with the order the jars are loaded. There is a version confilict with some classes. A common workaround is to rename parser.jar into zparser.jar, so it is loaded after xalan.jar and xerces.jar. This worked for me. -markus - Original Message - From: Betty Chang To: [EMAIL PROTECTED] Sent: Wednesday, July 04, 2001 5:34 AM Subject: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar? Hi -- I'm running a servlet application that uses the apache-XML xalan.jar and xerces.jar files for handling XML/XSL stuff. With tomcat 3.2.1, when I run my servlet, I get NoSuchMethodError on getNamespaceURI(), called by org.apache.xpath.DOM2Helper.getNamespaceOfNode(). I solved this problem by removing the jaxp.jar and parser.jar files that come with the tomcat installation and sit under the lib directory. The servlet still runs without those jar files, so the xalan.jar and xerces.jar must do the trick. Is there some kind of version conflict that causes the NoSuchMethodError? Thanks Betty
