Try removing parser.jar from the $TOMCAT_HOME/lib directory. If that
doesn't work, try placing jdom.jar in $TOMCAT_HOME/lib. I know it is
not convenient, but strangely it has solved my problem. It seems that
Tomcat appends webapp local classpath items to the globally defined
classpath when a prepend would be appropriate.
Cheers,
-Matt
-----Original Message-----
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org]
On Behalf Of Gary Bentley
Sent: Wednesday, March 21, 2001 7:10 AM
To: jdom-interest at jdom.org
Subject: [jdom-interest] Tomcat and JDOM
Hi folks,
Probably a simple answer but I'm a bit baffled...
How do I get Tomcat and JDOM 6 to work together? Keep getting:
org.jdom.JDOMException: Error in building: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
Now I can get it to work with JServ...
On Tomcat, I have jaxp.jar, jdom.jar and crimson.jar in the WEB-INF/lib
directory...maybe this is a question for the Tomcat mailing list but I'm
trying here first...
Also, I have expanded the jars into the WEB-INF/classes directory as
well...
Now I know that the org.apache.xerces directory is not present (I
checked
the Jar)...so why is JDOM looking for it...isn't it supposed to use JAXP
by
default now and it should be able to find that...it shoudn't be a class
loader problem since Tomcat is supposed to use a different class loader
per
web application...
Cheers (hopefully!),
G.
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@you
rhost.com