SOA composite is sending an empty SOAP 'header' element in 11g
(Doc ID 2134573.1)
Last updated on MARCH 28, 2019
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Some web services reject SOAP requests that contain the 'header' element in the SOAP message, even when the element is empty, and this is fine per the spec where it's stated that the header element is optional. SOA 11g is always sending the header element when invoking a service, even when it's empty, and this can cause some web services to reject the request.
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