[
https://jira.jboss.org/jira/browse/TEIID-644?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-644:
--------------------------------------
Looking at the SAXBuilder source, the parser search order is defined as:
saxDriverClass - which is not set because it needs to passed in the constructor.
then use JAXP 1.1 - which works for me locally on my JRE 1.6, but must be failing for
you.
then look for org.apache.xerces.parsers.SAXParser
So the question is, what JVM are you running and does it have a proper JAXP 1.1? In any
case I think we can safely move on with the release as this seems platform dependent.
XML-Relational connector is failing to load a SAX parser.
---------------------------------------------------------
Key: TEIID-644
URL:
https://jira.jboss.org/jira/browse/TEIID-644
Project: Teiid
Issue Type: Bug
Components: XML Connector
Affects Versions: 6.1.0
Environment: Teiid M4 on RHEL CSB called from SQuirreL
Reporter: John Doyle
Assignee: John Doyle
Fix For: 6.1.0
In the past the connector inherited xerces. I think it may need to be added to the
connector classpath.
Caused by: org.jdom.JDOMException: Could not load default SAX parser:
org.apache.xerces.parsers.SAXParser: SAX2 driver class org.apache.xerces.parsers.SAXParser
not found: org.apache.xerces.parsers.SAXParser
at org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:581)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:424)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:851)
at com.metamatrix.connector.xml.base.ExecutionInfo.getNamespaces
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira