Issue with the XSL Engine and OWSM Policy

Last updated on OCTOBER 24, 2017

Applies to:

Symptoms

On : 11.1.1.7.0 version, OSB Build

Issues with the combination of XSL engine and OWSM policy (wss_username_token_client_policy).

Initially, a Business Service that is configured with the OWSM policy (wss_username_token_client_policy) works fine but encountered problems after adding complex XSL transformations.

Problem1: “OSB Assign action failed updating variable "body": java.lang.RuntimeException: Invalid conversion from 'org.apache.xmlbeans.impl.store.Xobj$ElementXobj' to 'node-set'.”

This is a known issue and it only occurs when XSL needs to parse multiple sources. Oracle provides a solution (Document Id 1298039.1) already. The solution is a JVM parameter to switch to the WLS xsl engine. We have been using the solution for several projects already and worked well. However, the problem occurs when used this solution with OWSM together.

After Applying solution for Problem 1, the following problem (Problem 2) occurs:

Problem 2: “java.lang.RuntimeException: com.bea.wli.config.component.NotFoundException: Can not compute effective WSDL /*….”

Once the managed server is restarted with the new parameter, the business service stopped working.

When the debug button is clicked to activate the test console in sbconsole, the above messages appears on the "test console"

It turns out to be the combination of the “better” XSL engine and OWSM policy. 

Cause