Last updated on SEPTEMBER 09, 2017
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When a Composite A invokes Composite B exposed through Direct Binding and the BPEL callee within Composite B replies with custom fault message, the BPEL Caller in Composite A receives a BPEL remoteFault exception. Custom fault message details are lost. Note, that the business fault is already existent in the component's WSDL.
If the same scenario uses the WS Binding, the custom fault is returned through the <reply> activity.
Due to this issue, it is not possible to implement a component accessible through different bindings, as the fault handling cannot be implemented consequently.
Composite B replies with custom fault message and Composite A receives the custom fault message. The business fault should be returned as it is defined in the component's WSDL.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms