[teiid-issues] [JBoss JIRA] Resolved: (TEIID-644) XML-Relational connector is failing to load a SAX parser.
[
https://jira.jboss.org/jira/browse/TEIID-644?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-644.
----------------------------------
Resolution: Done
elevated jdom, commons-logging, and log4j to the provided scope and allow them to use the
engine's versions.
removed the specific inclusion of javax.servlet, since it is now being transitively
brought in by jetty.
added an exclusion for xml-apis to xalan
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