Not sure if this is related to your problem, but afaik, the createInstance
parameter
specifies that the bpel engine has to create a new process instance. I ' m
not
a BPEL expert, but with such a script, I think you will not be able to
correlate the two
messages, as two processes will be created.
Cheers,
Guillaume Nodet
On 6/29/06, KevinC <[EMAIL PROTECTED]> wrote:
BPEL 1.1 specification states that a flow completes when all of the
activities in the flow have completed.
So I try to use "flow" to receive two requests concurrently as follows:
<bpel:correlationSets>
<bpel:correlationSet name="tradeIdentifier"
properties="tns:tradeCorr"/>
</bpel:correlationSets>
<bpel:sequence>
<bpel:flow>
<bpel:receive name="getPurchaserDataImpl"
partnerLink="purchaserLT"
portType="tns:tradingPortType" operation="getPurchaserData"
variable="request1" createInstance="yes">
<bpel:correlations>
<bpel:correlation set="tradeIdentifier"
initiate="yes"/>
</bpel:correlations>
</bpel:receive>
<bpel:receive name="getSellerDataImpl"
partnerLink="sellerLT"
portType="tns:tradingPortType" operation="getSellerData"
variable="request2"
createInstance="yes">
<bpel:correlations>
<bpel:correlation set="tradeIdentifier"
initiate="yes"/>
</bpel:correlations>
</bpel:receive>
</bpel:flow>
<bpel:assign>
... <!-- copy values from above varaiables request1 & request2 -->
</bpel:assign>
</bpel:sequence>
However when I feed in one requeset message only, the assignment code will
still be executed.
Is there any problem with the BPEL syntax? How can I wait for both
requests
and correlate together before proceeding to the assignment part?
Thanks
--
View this message in context:
http://www.nabble.com/flow-and-correlation-tf1866019.html#a5098445
Sent from the ServiceMix - User forum at Nabble.com.
