My Oracle Support Banner

Jdeveloper Sets Incorrect Bpelx Variable When Sending Soap Headers (Doc ID 1360547.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.4.0 and later
Information in this document applies to any platform.

Symptoms

One superficial symptom is that when invoking an external service you get the following error:

<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Invalid SOAP Header</summary>
</part>
<part name="detail">
<detail>javax.xml.ws.soap.SOAPFaultException: Invalid SOAP Header</detail>
</part>
<part name="code">
<code>soap:Client</code>
</part>
</remoteFault>
</bpelFault>
</fault>
<faultType>
<message>0</message>
</faultType>

What you can actually notice if you investigate further is that JDeveloper incorrectly sets the "bpelx:" header variable to bpelx:headerVariable instead of bpelx:inputHeaderVariable

According to the documentation found in:
Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite
11g Release 1 (11.1.1)
Part Number E10224-01

Under section 7.19.2 How to Send SOAP Headers in BPEL , we can observe that the definition should be bpelx:inputHeaderVariable. The variable bpelx:headerVariable is used to receive SOAP Headers in BPEL.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.