[xep-support] SAX parser conflict

From: Conaway, Rob <Rob.Conaway@progressive-medical.com>
Date: Mon Apr 30 2007 - 06:46:56 PDT

I am embedding XEP in a Java application that also uses Hibernate 2.
When I include the XEP.jar in my project, I get the following messages
from Hibernate:
Warning: Caught exception attempting to use SAX to load a SAX XMLReader
Warning: Exception was: org.xml.sax.SAXException: System property
org.xml.sax.driver not specified
- problem parsing configuration/hibernate.cfg.xml
org.dom4j.DocumentException: Could not initialize a SAX Parser. Please
add a SAX parser to your classpath along with preferably jaxp.jar

Although I don't include SAXON.jar explicitly, XEP.jar refers to it in
its MANIFEST.MF file. When I remove SAXON.jar from the class path,
everything seems to work fine.

I am using JDK 1.4 which I believe uses Xalan as the default parser.
Since I have done all my testing to this point using Xalan, I'd like to
avoid bringing in a different SAX parser (which I am apparently doing
when saxon.jar is on the classpath).

Is there any reason why XEP requires SAXON.jar when using JDK 1.4? As I
said, everything seems to be working but I don't want to hit a wall

Thank you for you help,

Rob Conaway
Progressive Medical, Inc.

(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Mon Apr 30 07:08:50 2007

This archive was generated by hypermail 2.1.8 : Mon Apr 30 2007 - 07:08:54 PDT