[
https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou resolved ODE-410.
-------------------------------
Resolution: Fixed
Assignee: Matthieu Riou
Patch committed on 1.X, thanks!
Can you also create another issue for the trunk merge?
> Support multiple matching correlation sets on IMAs
> --------------------------------------------------
>
> Key: ODE-410
> URL: https://issues.apache.org/jira/browse/ODE-410
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Reporter: Sean Ahn
> Assignee: Matthieu Riou
> Fix For: 1.3
>
> Attachments: ode-410.patch
>
>
> WS-BPEL 2.0 spec specifies on how multiple matching correlation sets should
> be handled in section 9.2.
> When multiple correlation sets are used in an IMA with initiate="no", a
> message MUST match all such correlation sets for that message to be delivered
> to the activity in the given process instance.
> Currently, ODE supports multiple initiating correlation sets but supports
> only one matching correlation set. The change includes:
> 1. On an IMA, when multiple correlation sets are specified, all the
> initiating correlation sets should be created newly and the remaining
> correlation sets that are not bound to correlation keys should be used as a
> combined key to match to an instance.
> 2. Instead of a single CorrelationKey object, a set of CorrelationKeys should
> be used in serializing the key set to database and in comparing against set
> of correlation set values from the incoming message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
