BPEL Automatically Creates Blank Namespaces (Doc ID 823462.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.3.0 to 10.1.3.4.0
This problem can occur on any platform.

Symptoms

Using BPEL 10.1.3.4 MLR#6, BPEL Processes call web services via SOAP. In this case the wsdl message has two elements, the types of these elements refer to two different namespaces in two different xsd's.
For ex:

<xsd:element name="icrm_cust_cnfrmReg">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="messageHeader" type="mh:messageHeaderType"/>
<xsd:element name="icrm_cust_cnfrmReg_type"
type="fm:icrm_cust_cnfrmReg_type"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>


If we invoke the WSDL through the BPEL Console (or initiate the BPEL Process from SOAPUI), BPEL automatically adds a blank namespace to the elements:
<messageHeader xmlns="">
....
</messageHeader>
<icrm_cust_cnfrmReg_type xmlns="">
....
</icrm_cust_cnfrmReg_type>



Cause

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