Closed as program error.
Error during service invocation from a business process where imports use relative path : com.ibm.bpe.api.ProcessError: Error during deserialization java.io.IOException: WSDLException (at /definitions/import): faultCode=OTHER_ERROR: An error Occurred trying to resolve schema referenced at 'abc.xsd', relative to 'file:jp/../xyz.xsd'
When the business process runs, the service definition is resolved to invoke the corresponding service. The way referenced WSDL/XSD resources are resolved when the base URL comprises only a relative URL is incorrect. As a result, the resource cannot be resolved and the invocation of the service fails when the business process is executed. A business process that invokes a service can fail with an exception that looks like this: com.ibm.bpe.util.TraceLog.trace(TraceLog.java:82) The following exception was logged com.ibm.bpe.api.ProcessError: Error during Deserialization java.io.IOException: WSDLException (at /definitions/import): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'SamEq1JText_1_DynMO.xsd', relative to 'file:jp/../eqk20d11sam.xsd'. at com.ibm.bpe.plugins.WSDLDefinition.readObject(WSDLDefinition.jav a:502)
With this interim fix, the way referenced WSDL/XSD resources are resolved is changed. Even if the base URL for this reference comprises only a relative URL, the reference can be resolved. NOTE: After you apply this fix, you must re-install all of the business processes that are affected. If you use process choreographer in an ND environment, you must apply this interim fix to the node manager. Problem fixed on top of 188.8.131.52
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels