Various SAXReader related errors

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1 EE SP3 (5.1.6), 5.2 EE SP1 (5.2.5)
• Fix Version/s: 5.1 EE SP4 (5.1.7), 5.2 EE SP2 (5.2.6)
• Component/s: None
• Labels:
  • 5.2_release_notes
• Environment: WebLogic

On WebLogic and possibly other application server, various SAXReader related errors such as the following may occur:

Error on line 3 of document : Document is invalid: no grammar found. Nested exception: Document is invalid: no grammar found.

WARN [SAXReaderImpl:444] XSD validation is diasabled because SAX2 driver class org.apache.xerces.parsers.SAXParser not found

Currently, Dom4j is instantiated via JAXP by passing in the class name "org.apache.xerces.parsers.SAXParser". Depending on the app server, JAXP would sometimes be located in the server classpath and would sometimes be located in the web app classpath. If JAXP is in the server classpath, xercesImpl.jar would also have to be in the server classpath. However, xercesImpl.jar is also included in the web app classpath. To resolve this issue, we now ensure JAXP is loaded from the web app classpath.