Error calling BPEL from ESB Multi-part simple type

Question

I am trying to define a soap service in ESB which is refering a BPEL service. I get the error
The selected porttype is using a message that is invalid for ESB because it is multi-part or has a simple type.The message RuntimeFaultMessage in operation process of port type exportCaCustomers is invalid. Please select another portype.
Here is the wsdl for the BPEL service. exportCaCustomers.wsdl
<definitions
name="exportCaCustomers"
targetNamespace="http://xmlns.oracle.com/exportCaCustomers"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:ns3="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd"
xmlns:ns2="http://schemas.oracle.com/bpel/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:client="http://xmlns.oracle.com/exportCaCustomers"
xmlns:ns10="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl"/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/exportCaCustomers">
<import namespace="http://xmlns.oracle.com/exportCaCustomers" schemaLocation="exportCaCustomers.xsd"/>
</schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/exportCaCustomers">
<xsd:import namespace="http://www.globalcompany.com/ns/order" schemaLocation="sampleTax.xsd"/>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd" schemaLocation="InputMessage.xsd"/>
</xsd:schema>
</types>
<message name="exportCaCustomersRequestMessage">
<part name="payload" element="ns10:CVInputMessage"/>
</message>
<message name="exportCaCustomersResponseMessage">
<part name="payload" element="client:exportCaCustomersProcessResponse"/>
</message>
<portType name="exportCaCustomers">
<operation name="process">
<input message="client:exportCaCustomersRequestMessage"/>
<output message="client:exportCaCustomersResponseMessage"/>
<fault name="bindingFault" message="ns2:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="exportCaCustomers">
<plnk:role name="exportCaCustomersProvider">
<plnk:portType name="client:exportCaCustomers"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
These are the contents of RuntimeFault.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
This looks like a very basic thing to do. My BPEL process is working fine. I just want to access it from ESB. Any ESB gurus there. Please respond.

Answer 1

<fault name="bindingFault" message="ns2:RuntimeFaultMessage"/>Don't think this is the way to define the RuntimeFaults.
the fault-element you use to 'throw' you own business faults.
RunTimeFaults are handled by the bpel framework itself and aren't throwable like this.
See :
http://www.oracle.com/technology/products/ias/bpel/htdocs/orabpel_technotes.tn007.html
""Business faults are application specific faults and occur when an explicit <throw> activity is executed or an <invoke> activity gets a fault as response. The fault name of a business fault is specified by the BPEL process and the messageType, if one exists, is defined in the WSDL.
Runtime faults are not user defined and will not appear in the WSDL for a process or service.""