Petals BC SOAP

When using WS-Policy in provide mode: ClassNotFoundException: org.apache.xml.utils.URI$MalformedURIException

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.0.7
  • Fix Version/s: 4.0.8
  • Component/s: None
  • Security Level: Public
  • Description:

    When enabling WS-Policy into a SOAP-provide SU to invoke an external secured webg-service, I get the following error: ClassNotFoundException: org.apache.xml.utils.URI$MalformedURIException

  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Sep 2011 - 11:37:43 +0200

The missing class is provided by Xalan that was excluded from the component packaging. Use the version 2.7.1 of xalan instead of 2.7.0 provided by Axis2 because of a bug about API Transformer.reset()

Show
Christophe DENEUX added a comment - Thu, 29 Sep 2011 - 11:37:43 +0200 The missing class is provided by Xalan that was excluded from the component packaging. Use the version 2.7.1 of xalan instead of 2.7.0 provided by Axis2 because of a bug about API Transformer.reset()
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Sep 2011 - 11:58:07 +0200

Fix in branch petals-entreprise-3.1.x

Show
Christophe DENEUX added a comment - Thu, 29 Sep 2011 - 11:58:07 +0200 Fix in branch petals-entreprise-3.1.x
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Sep 2011 - 11:58:57 +0200

To merge in trunk.

Caution: a potential conflict exists between Xalan and Saxon (if already the main XSLT engine of Petals 4)

Show
Christophe DENEUX added a comment - Thu, 29 Sep 2011 - 11:58:57 +0200 To merge in trunk. Caution: a potential conflict exists between Xalan and Saxon (if already the main XSLT engine of Petals 4)
Hide
Permalink
noddoux added a comment - Thu, 15 Dec 2011 - 15:32:12 +0100 - edited

Xalan 2.7.1 is already included in the version 4.1 to avoid the error ClassNotFoundException: org.apache.xml.utils.URI$MalformedURIException (when using WS-Security). Rampart probably uses this exception in its code. However, Xalan is not used as XSLT engine.

WS-Policy are not used any more in the version 4.1 to configure WS-Security (as it did not work correctly). The configuration of WS-Security is only possible with the parameters modules and service-parameters (http://doc.petalslink.com/display/petalscomponents/Petals-BC-SOAP+4.1.x).

Show
noddoux added a comment - Thu, 15 Dec 2011 - 15:32:12 +0100 - edited Xalan 2.7.1 is already included in the version 4.1 to avoid the error ClassNotFoundException: org.apache.xml.utils.URI$MalformedURIException (when using WS-Security). Rampart probably uses this exception in its code. However, Xalan is not used as XSLT engine. WS-Policy are not used any more in the version 4.1 to configure WS-Security (as it did not work correctly). The configuration of WS-Security is only possible with the parameters modules and service-parameters (http://doc.petalslink.com/display/petalscomponents/Petals-BC-SOAP+4.1.x).

People

Dates

  • Created:
    Thu, 29 Sep 2011 - 11:36:05 +0200
    Updated:
    Thu, 15 Dec 2011 - 15:33:35 +0100
    Resolved:
    Thu, 15 Dec 2011 - 15:33:35 +0100
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.