HTTP BINDING (Service Adapter) POST Sends SOAPAction In Header
(Doc ID 1531916.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle SOA Platform - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.0 version, BPEL Service Engine
When calling an external (People-Soft) process exposed via an HTTP Binding from SOA BPEL, the end point recognizes this call to be a SOAP call even though the call should be an HTTP one.
Further analysis shows that this is due to the fact that the BPEL is sending as the SOAPAction null in the Header (SOAPAction: "null")
When the endpoint sees this header property, it seems it thinks there is a soap message, but fails when there is correctly not a SOAP message (because this is not supposed to be a SOAP call).
A fix so that the SOAPAction is not sent for the HTTP Binding (POST) - a patch would be helpful
Steps to reproduce
The issue can be reproduced at will with the following steps:
- Create BPEL composite that invokes HTTP BINDING adapter (POST verb)
- Run tcpmon (or other tool to intercept message)
- Run an instance of the composite that will invoke the HTTP endpoint
- Examine the message (header properties) on the intercept tool
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document