onEventProcess.bpel

<bpel:process name="onEventProcess" targetNamespace="http://example.org/onEventProcess"
    suppressJoinFailure="yes"
    xmlns:tns="http://example.org/onEventProcess"
    xmlns:wsdl="http://example.org/onEventProcess/wsdl"
    xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable">
    <!-- Import the client WSDL -->
    <bpel:import location="onEventProcessArtifacts.wsdl"
        namespace="http://example.org/onEventProcess/wsdl" importType="http://schemas.xmlsoap.org/wsdl/" />

    <!--
        =================================================================
    -->
    <!--
        PARTNERLINKS
    -->
    <!--
        List of services participating in this BPEL process
    -->
    <!--
        =================================================================
    -->
    <bpel: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.
        -->
        <bpel:partnerLink name="client" partnerLinkType="wsdl:onEventProcess"
            myRole="onEventProcessProvider" partnerRole="onEventProcessRequester" />
    </bpel:partnerLinks>

    <!--
        =================================================================
    -->
    <!--
        VARIABLES
    -->
    <!--
        List of messages and XML documents used within this BPEL process
    -->
    <!--
        =================================================================
    -->
    <bpel:variables>
        <!-- Reference to the message passed as input during initiation -->


        <!-- Reference to the message that will be sent back to the
             requester during callback
             -->
        <bpel:variable name="output"
            messageType="wsdl:onEventProcessResponseMessage"/>
        <bpel:variable name="clientRequest"
             element="wsdl:onEventProcessRequest"/>


    </bpel:variables>

    <!--
        =================================================================
    -->
    <!--
        ORCHESTRATION LOGIC
    -->
    <!--
        Set of activities coordinating the flow of messages across the
    -->
    <!--
        services integrated within this business process
    -->
    <!--
        =================================================================
    -->
    <bpel:sequence name="main">

        <!--
            Receive input from requestor. Note: This maps to operation defined in
            onEventProcess.wsdl
        -->
        <bpel:receive name="receiveInput" partnerLink="client"
            portType="tns:onEventProcess" operation="initiate" variable="input"
            createInstance="yes" />
        <bpel:empty name="FIX_ME-Add_Business_Logic_Here"></bpel:empty>
        <!--
            Asynchronous callback to the requester. Note: the callback location
            and correlation id is transparently handled using WS-addressing.
        -->
        <bpel:invoke name="callbackClient" partnerLink="client"
            portType="tns:onEventProcessCallback" operation="onResult"
            inputVariable="output" />
    </bpel:sequence>

    <bpel:eventHandlers>
        <bpel:onEvent partnerLink="client" operation="wsdl:initiate" portType="wsdl:onEventProcess"
             variable="clientVar" element="wsdl:onEventProcessRequest" messageType="wsdl:onEventProcessRequestMessage">
            <!--
            <bpel:fromParts>
                <bpel:fromPart part="" toVariable=""/>
            </bpel:fromParts>
            -->
            <bpel:scope>
                <bpel:variables>
                    <bpel:variable name="scopeVar" messageType="wsdl:onEventProcessRequestMessage"/>
                </bpel:variables>
            </bpel:scope>
        </bpel:onEvent>
    </bpel:eventHandlers>
</bpel:process>