jbi.messaging.MessagingException using BPEL

classic Classic list List threaded Threaded
11 messages Options
Ice
Reply | Threaded
Open this post in threaded view
|

jbi.messaging.MessagingException using BPEL

Ice
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

jlesbegueries
Hi,

I see in the assign some strange expressions (null elements):

$CalculatorPartnerRequest.requestBPEL/null:p1...

Did you use the PetalsStudio or Eclipse with BPEL plugin to edit your BPEL?
There is an helper to build your assignments (I advise you to use the "Expression" way).

Can you provide the complete SA.zip of your BPEL and potential WSDLs used?

Thank you,
Julien.

Ice
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

Ice
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

jlesbegueries
Hi,

In the BPEL I saw that you missed to set the createInstance to yes (thanks to PetalsStudio).
And I tried also to improve the assignement expressions.

Here is the updated BPEL. Can you try it?

Calculator.bpel
Best,
Julien.
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

jlesbegueries
Not sure about the link to the BPEL file. Here it is plain text:

<process name="Calculator" targetNamespace="http://petals.ow2.org/bpel/Calculator/"
	xmlns:tns="http://petals.ow2.org/bpel/Calculator/" xmlns:artifacts="http://petals.ow2.org/bpel/Calculator/Artifacts"
	xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
	xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable" xmlns:ns1="http://www.example.org/CalculatorXMLSchema">

	<!-- Import the client WSDL -->
	<import location="CalculatorDefinition.wsdl" namespace="http://petals.ow2.org/bpel/Calculator/"
		importType="http://schemas.xmlsoap.org/wsdl/" />

	<import location="CalculatorArtifacts.wsdl"
		namespace="http://petals.ow2.org/bpel/Calculator/Artifacts"
		importType="http://schemas.xmlsoap.org/wsdl/" />

	<!-- ================================================================= -->
	<!-- PARTNERLINKS -->
	<!-- List of services participating in this BPEL process -->
	<!-- ================================================================= -->
	<partnerLinks>
		<!-- The 'client' role represents the requester of this service. -->
		<partnerLink name="CalculatorPartner" partnerLinkType="artifacts:CalculatorPartnerLink"
			myRole="CaclulatorPartnerLinkRole" />
        
    </partnerLinks>

	<!-- ================================================================= -->
	<!-- VARIABLES -->
	<!-- List of messages and XML documents used within this BPEL process -->
	<!-- ================================================================= -->
	<variables>
		<bpel:variable name="CalculatorPartnerRequest"
			messageType="tns:CalculatorRequestMessage" />
		<bpel:variable name="CalculatorPartnerResponse"
			messageType="tns:CalculatorResponseMessage"></bpel:variable>
	</variables>

	<!-- ================================================================= -->
	<!-- ORCHESTRATION LOGIC -->
	<!-- Set of activities coordinating the flow of messages across the -->
	<!-- services integrated within this business process -->
	<!-- ================================================================= -->
	<sequence name="MainSequence">
		<bpel:receive name="ReceiveMessage" partnerLink="CalculatorPartner"
			operation="processBPEL" portType="tns:CalculatorPortType" variable="CalculatorPartnerRequest" createInstance="yes"/>
		<assign name="Assign1">
			
            <bpel:copy>
                <bpel:from>
                    
                    
                    
                    <![CDATA[($CalculatorPartnerRequest.requestBPEL/ns1:p1 + $CalculatorPartnerRequest.requestBPEL/ns1:p2)/($CalculatorPartnerRequest.requestBPEL/ns1:p3)]]>
                </bpel:from>
                <bpel:to>
                    <![CDATA[$CalculatorPartnerResponse.responseBPEL/ns1:result]]>
                </bpel:to>
            </bpel:copy>
        </assign>
		<bpel:reply name="Reply" partnerLink="CalculatorPartner"
			operation="processBPEL" portType="tns:CalculatorPortType" faultName="tns:faultBPEL"
			variable="CalculatorPartnerResponse"></bpel:reply>
	</sequence>
</process>
Ice
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

Ice
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

jlesbegueries
Hi,

Indeed I had a doubt also, did you try with div?

Do you have the SOAP consume SA in order to test the BPEL with SOAPUI for instance?

Julien.
Ice
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

Ice
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

jlesbegueries
Hi,

when I test the BPEL I sent to you with div instead of /, I've got a computation made only between p2 and p3 ... I'm checking why the BPEL expression does not take into account p1 and then I will send you
1/ the su BPEL that contains BPEL files and generate BPEL endpoint and 2/ su SOAP Consume that exposes this BPEL endpoint outside the bus, as a Web Service, invoked by SOAPUI...

I try to give you the solution on Monday of next week.

Best,
Julien.
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

jlesbegueries
Hi,

Finally the BPEL worked for me,
I provide hereafter a link to a SA composed of a SU-BPEL-provide providing the orchestration and the SU-SOAP-consume that exposes the BPEL service outside the bus. Once this SA is deployed, you can send a request with SOAPUi for instance, on the exposed address.

Here is a link to the SA and SOAPUi projects files to help you: http://jul64.free.fr/bpel/bpel-ice/ 

With a default configuration the endpoint of the exposed WS should be:

http://localhost:8084/petals/services/CalculatorPortType

and an example of request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cal="http://www.example.org/CalculatorXMLSchema">
   <soapenv:Header/>
   <soapenv:Body>
      <cal:params>
  	    <cal:p1>5</cal:p1>
         <cal:p2>5</cal:p2>
         <cal:p3>3</cal:p3>
      </cal:params>
   </soapenv:Body>
</soapenv:Envelope>

It worked for me with petals-esb 4.2.0, petals-bc-soap 4.3.0, and petals-se-bpel 1.2.0-SNAPSHOT (compiled from the trunk of petals).

Best,
Julien.
Ice
Reply | Threaded
Open this post in threaded view
|

Re: jbi.messaging.MessagingException using BPEL

Ice
CONTENTS DELETED
The author has deleted this message.