Petals BC SOAP

Error "SAX2 driver class org.apache.xerces.parsers.SAXParser not found" when installing a service unit

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.2.0
  • Fix Version/s: 4.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The error "SAX2 driver class org.apache.xerces.parsers.SAXParser not found" occurs when installing a service unit:

    org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
	at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:188)
	at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:116)
	at org.ow2.petals.component.framework.util.WSDLUtilImpl.createWsdlDescription(WSDLUtilImpl.java:249)
	at org.ow2.petals.component.framework.util.WSDLUtilImpl.createWsdlDescription(WSDLUtilImpl.java:219)
	at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.getWsdlDescription(AbstractServiceUnitManager.java:134)
	... 20 more
    Show
    The error "SAX2 driver class org.apache.xerces.parsers.SAXParser not found" occurs when installing a service unit: 
    org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
	at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:188)
	at org.ow2.easywsdl.extensions.wsdl4complexwsdl.impl.inout.WSDL4ComplexWsdlReaderImpl.read(WSDL4ComplexWsdlReaderImpl.java:116)
	at org.ow2.petals.component.framework.util.WSDLUtilImpl.createWsdlDescription(WSDLUtilImpl.java:249)
	at org.ow2.petals.component.framework.util.WSDLUtilImpl.createWsdlDescription(WSDLUtilImpl.java:219)
	at org.ow2.petals.component.framework.su.AbstractServiceUnitManager.getWsdlDescription(AbstractServiceUnitManager.java:134)
	... 20 more
  • Environment:
    Petals ESB is running with JavaSE 7

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Thu, 19 Jun 2014 - 14:58:21 +0200

As mentionned here: http://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven, xercesImpl should not be provided be the BC Soap

Show
Christophe DENEUX added a comment - Thu, 19 Jun 2014 - 14:58:21 +0200 As mentionned here: http://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven, xercesImpl should not be provided be the BC Soap
Hide
Permalink
Christophe DENEUX added a comment - Thu, 19 Jun 2014 - 16:20:39 +0200

Dependency xercesImpl removed in trunk

Show
Christophe DENEUX added a comment - Thu, 19 Jun 2014 - 16:20:39 +0200 Dependency xercesImpl removed in trunk
Hide
Permalink
Christophe DENEUX added a comment - Tue, 16 Sep 2014 - 11:30:57 +0200

Workaround:

  • for Petals ESB 4.1.x: add the following parameter to the startup script,
  • for Petals ESB 4.2.x: add the following parameter to your environment file ($PETALS_HOME/conf/env.sh).
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
Show
Christophe DENEUX added a comment - Tue, 16 Sep 2014 - 11:30:57 +0200 Workaround:
  • for Petals ESB 4.1.x: add the following parameter to the startup script,
  • for Petals ESB 4.2.x: add the following parameter to your environment file ($PETALS_HOME/conf/env.sh).
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser

People

Dates

  • Created:
    Thu, 19 Jun 2014 - 14:53:26 +0200
    Updated:
    Tue, 16 Sep 2014 - 11:30:57 +0200
    Resolved:
    Thu, 19 Jun 2014 - 16:20:39 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.