SOA composite is sending an empty SOAP 'header' element in 11g
Last updated on AUGUST 09, 2016
Applies to:Oracle SOA Suite - Version 188.8.131.52.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.
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