Mutliple wsdl operations for a port in BPEL Project -- Help

Question

I was trying to create a BPEL project with multiple operations for one port type. I used a pick activity and on message acitivity to branch out based on the operation. For some reason all the operations are channeled through the same branch (operation). Please share with me your experiences and any simple project.
-----------------wsdl file -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="MultiWsdl"
targetNamespace="http://xmlns.oracle.com/MultiWsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/MultiWsdl"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TYPE DEFINITION - List of services participating in this BPEL process
The default output of the BPEL designer uses strings as input and
output to the BPEL Process. But you can define or import any XML
Schema type and use them as part of the message types.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/MultiWsdl" schemaLocation="MultiWsdl.xsd" />
</schema>
</types>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<message name="MultiWsdlRequestMessage">
<part name="payload" element="client:MultiWsdlProcessRequest"/>
</message>
<message name="MultiWsdlResponseMessage">
<part name="payload" element="client:MultiWsdlProcessResponse"/>
</message>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
*<!-- portType implemented by the MultiWsdl BPEL process -->
*<portType name="MultiWsdl">
*<operation name="Create">
*<input message="client:MultiWsdlRequestMessage"/>
*<output message="client:MultiWsdlResponseMessage"/>
*</operation>
*<operation name="Update">
*<input message="client:MultiWsdlRequestMessage"/>
*<output message="client:MultiWsdlResponseMessage"/>
*</operation>
*</portType>
<!-- portType implemented by the requester of MultiWsdl BPEL process
for asynchronous callback purposes
-->
<portType name="MultiWsdlCallback">
<operation name="TestReply">
<input message="client:MultiWsdlResponseMessage"/>
</operation>
</portType>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
the MultiWsdl partnerLinkType binds the provider and
requester portType into an asynchronous conversation.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="MultiWsdl">
<plnk:role name="MultiWsdlProvider">
<plnk:portType name="client:MultiWsdl"/>
</plnk:role>
<plnk:role name="MultiWsdlRequester">
<plnk:portType name="client:MultiWsdlCallback"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
---------------- Bpel File ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
<?xml version = "1.0" encoding = "UTF-8" ?>
<!--
Oracle JDeveloper BPEL Designer
Created: Thu Nov 06 21:46:50 PST 2008
Author:
Purpose: Asynchronous BPEL Process
-->
<process name="MultiWsdl" targetNamespace="http://xmlns.oracle.com/MultiWsdl"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/MultiWsdl"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<!--
PARTNERLINKS
List of services participating in this BPEL process
-->
<partnerLinks>
<!--
The 'client' role represents the requester of this service. It is
used for callback. The location and correlation information associated
with the client role are automatically set using WS-Addressing.
-->
<partnerLink name="client" partnerLinkType="client:MultiWsdl"
myRole="MultiWsdlProvider"
partnerRole="MultiWsdlRequester"/>
</partnerLinks>
<!--
VARIABLES
List of messages and XML documents used within this BPEL process
-->
<variables>
<!-- Reference to the message passed as input during initiation -->
<variable name="inputVariable"
messageType="client:MultiWsdlRequestMessage"/>
<!-- Reference to the message that will be sent back to the requester during callback -->
<variable name="outputVariable"
messageType="client:MultiWsdlResponseMessage"/>
<variable name="OnMessage_TestReq_InputVariable"
messageType="client:MultiWsdlRequestMessage"/>
<variable name="OnMessage_TestReq_InputVariable_1"
messageType="client:MultiWsdlRequestMessage"/>
<variable name="Reply_2_TestReq_OutputVariable"
messageType="client:MultiWsdlResponseMessage"/>
<variable name="Reply_1_TestReq_OutputVariable"
messageType="client:MultiWsdlResponseMessage"/>
</variables>
<!--
ORCHESTRATION LOGIC
Set of activities coordinating the flow of messages across the
services integrated within this business process
-->
<sequence name="main">
<!-- Receive input from requestor. (Note: This maps to operation defined in MultiWsdl.wsdl) -->
<!--
Asynchronous callback to the requester. (Note: the callback location and correlation id is transparently handled using WS-addressing.)
-->
<pick name="Pick_1" createInstance="yes">
<onMessage portType="client:MultiWsdl" operation="Update"
variable="OnMessage_TestReq_InputVariable_1"
partnerLink="client">
<sequence name="Sequence_1">
<assign name="Assign_1">
<copy>
<from expression="'test'"/>
<to variable="Reply_1_TestReq_OutputVariable"
part="payload"
query="/client:MultiWsdlProcessResponse/client:result"/>
</copy>
</assign>
<reply name="Reply_2" partnerLink="client"
portType="client:MultiWsdl" operation="Update"
variable="Reply_1_TestReq_OutputVariable"/>
</sequence>
</onMessage>
<onMessage portType="client:MultiWsdl" operation="Create"
variable="OnMessage_TestReq_InputVariable"
partnerLink="client">
<sequence name="Sequence_2">
<assign name="Assign_2">
<copy>
<from expression='"AB"'/>
<to variable="Reply_2_TestReq_OutputVariable"
part="payload"
query="/client:MultiWsdlProcessResponse/client:result"/>
</copy>
</assign>
<reply name="Reply_1" partnerLink="client"
portType="client:MultiWsdl" operation="Create"
variable="Reply_2_TestReq_OutputVariable"/>
</sequence>
</onMessage>
</pick>
</sequence>
</process>
----------xsd -------
<schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/MultiWsdl"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="MultiWsdlProcessRequest">
<complexType>
<sequence>
<element name="input" type="string"/>
</sequence>
</complexType>
</element>
<element name="MultiWsdlProcessResponse">
<complexType>
<sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
</schema>
-----------------------------------------------------------------------------------------------------bpel.xml--------------------------------------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="MultiWsdl" src="MultiWsdl.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">MultiWsdl.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>

Answer 1

Thanks a lot. It helped me a lot. It seems this is the problem with the BPEL Console. I tried to create another BPEL Project to invoke the other service/operations. It worked perfectly fine. I had even tested with SoapUI. It worked fine. Thanks for the right pointer.