You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Sean Ahn (JIRA)" <ji...@apache.org> on 2008/11/05 22:58:44 UTC
[jira] Created: (ODE-410) Support multiple matching correlation
sets on IMAs
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
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.
[jira] Updated: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-410:
-------------------------
Attachment: ode-410.patch
Attached patch file.
> 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
> 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.
[jira] Updated: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-410:
-------------------------
Attachment: (was: ode-410.patch)
> 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
> Fix For: 1.3
>
>
> 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.
[jira] Updated: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-410:
-------------------------
Attachment: ode-410.patch
This patch ignores the two test cases in the PubSubTest
> 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
> 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.
[jira] Commented: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649243#action_12649243 ]
Sean Ahn commented on ODE-410:
------------------------------
Please revive the testPubSubInProc() in bpel-test/src/test/java/org/apache/ode/test/PubSubTest.java by taking out the @Ingore annotation from the method.
Only the other testPubSubOutOfProc() test in the same class is failing.
> 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
> 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.
[jira] Commented: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649522#action_12649522 ]
Sean Ahn commented on ODE-410:
------------------------------
Thanks, Matthieu!
Another issue has been created fro the trunk migration tracking:
https://issues.apache.org/jira/browse/ODE-433
> 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.
[jira] Commented: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648657#action_12648657 ]
Matthieu Riou commented on ODE-410:
-----------------------------------
The patch looks good but after applying it locally I get failures in PubSubTest (in the bpel-test module).
[junit] Invocation#/home/mriou/dev/projects/ode-1.X/bpel-test/target/test-classes/bpel/2.0/TestPubSubOutOfProc/test2.properties#1: Unexpected final message exchange status; got ASYNC, expected RESPONSE
[junit]
[junit] at org.apache.ode.test.BPELTestAbstract.checkFailure(BPELTestAbstract.java:281)
[junit] at org.apache.ode.test.BPELTestAbstract.go(BPELTestAbstract.java:269)
[junit] at org.apache.ode.test.BPELTestAbstract.go(BPELTestAbstract.java:206)
[junit] at org.apache.ode.test.BPELTestAbstract.go(BPELTestAbstract.java:191)
[junit] at org.apache.ode.test.PubSubTest.testPubSubOutOfProc(PubSubTest.java:30)
[junit]
[junit] Test org.apache.ode.test.PubSubTest FAILED
> 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
> 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.
[jira] Resolved: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-410:
-------------------------
Attachment: ode-410.patch
A new patch has been attached with the message arriving before the receive operation problem has been addressed.
> 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
> 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.
[jira] Updated: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-410:
-------------------------
Attachment: (was: ode-410.patch)
> 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
> Fix For: 1.3
>
>
> 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.
[jira] Updated: (ODE-410) Support multiple matching correlation
sets on IMAs
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou updated ODE-410:
------------------------------
Fix Version/s: (was: 2.0)
1.3
> 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
> Fix For: 1.3
>
>
> 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.