.wsdl for Caller Process

gistfile1.xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<definitions name="CallerProcess"
        xmlns="http://schemas.xmlsoap.org/wsdl/"
        xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:tns="http://caller.com"
        xmlns:ns1="http://async.com"
        targetNamespace="http://caller.com"
      >

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     TYPE DEFINITION - List of types participating in this BPEL process 
     The BPEL Designer will generate default request and response types
     but you can define or import any XML Schema type and use them as part 
     of the message types.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
    <types>
        <schema attributeFormDefault="unqualified" elementFormDefault="qualified" 
                targetNamespace="http://caller.com" 
                xmlns="http://www.w3.org/2001/XMLSchema">

            <element name="CallerProcessRequest">
                <complexType>
                    <sequence>
                        <element name="input" type="string"/>
                    </sequence>
                </complexType>
            </element>

            <element name="CallerProcessResponse">
                <complexType>
                    <sequence>
                        <element name="result" type="string"/>
                    </sequence>
                </complexType>
            </element>
        </schema>
    </types>


<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     MESSAGE TYPE DEFINITION - Definition of the message types used as 
     part of the port type defintions
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
    <message name="CallerProcessRequestMessage">
        <part name="payload" element="tns:CallerProcessRequest"/>
    </message>
    <message name="CallerProcessResponseMessage">
        <part name="payload" element="tns:CallerProcessResponse"/>
    </message>

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PORT TYPE DEFINITION - A port type groups a set of operations into
     a logical service unit.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    

    <!-- portType implemented by the CallerProcess BPEL process -->
    <portType name="CallerProcess">
        <operation name="process">
            <input  message="tns:CallerProcessRequestMessage" />
            <output message="tns:CallerProcessResponseMessage"/>
        </operation>
    </portType>   
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PARTNER LINK TYPE DEFINITION
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
    <plnk:partnerLinkType name="CallerProcess">
        <plnk:role name="CallerProcessProvider" portType="tns:CallerProcess"/>
    </plnk:partnerLinkType>


    
<vprop:property name="property" type="xsd:string"/>
  
    <vprop:propertyAlias messageType="tns:CallerProcessRequestMessage" part="payload" propertyName="tns:property">
    <vprop:query><![CDATA[/tns:input]]></vprop:query>
  </vprop:propertyAlias>
    <vprop:propertyAlias messageType="tns:CallerProcessResponseMessage" part="payload" propertyName="tns:property">
    <vprop:query><![CDATA[/tns:result]]></vprop:query>
  </vprop:propertyAlias>
    <vprop:propertyAlias messageType="ns1:AsynchProcessRequestMessage" part="payload" propertyName="tns:property">
    <vprop:query><![CDATA[/ns1:input]]></vprop:query>
  </vprop:propertyAlias>
    <vprop:propertyAlias messageType="ns1:AsynchProcessResponseMessage" part="payload" propertyName="tns:property">
    <vprop:query><![CDATA[/ns1:result]]></vprop:query>
  </vprop:propertyAlias>

<vprop:property name="flow_property" type="xsd:string"/>
<vprop:propertyAlias messageType="ns1:AsynchProcessRequestMessage" part="payload" propertyName="tns:flow_property">
    <vprop:query><![CDATA[/ns1:flow_number]]></vprop:query>
  </vprop:propertyAlias>
    <vprop:propertyAlias messageType="ns1:AsynchProcessResponseMessage" part="payload" propertyName="tns:flow_property">
    <vprop:query><![CDATA[/ns1:flow_number]]></vprop:query>
  </vprop:propertyAlias>

<import location="AsynchProcessArtifacts.wsdl" namespace="http://async.com"/>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     BINDING DEFINITION - Defines the message format and protocol details
     for a web service.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <binding name="CallerProcessBinding" type="tns:CallerProcess">
      <soap:binding style="document"
    		transport="http://schemas.xmlsoap.org/soap/http" />
    	<operation name="process">
    		<soap:operation
    			soapAction="http://caller.com/process" />
    		<input>
    			<soap:body use="literal" />
    		</input>
    		<output>
    			<soap:body use="literal" />
    		</output>
    	</operation>
    </binding>

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     SERVICE DEFINITION - A service groups a set of ports into
     a service unit.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <service name="CallerProcessService">
    	<port name="CallerProcessPort" binding="tns:CallerProcessBinding">
    		<soap:address location="http://localhost:8080/ode/processes/CallerProcess" />
    	</port>
    </service>
</definitions>