[jira] Commented: (ODE-262) Duplicated correlation set values is accepted and creates a second instance instead of throwing an exception

["Karthick Sankarachary (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652113#action_12652113 ] 

Karthick Sankarachary commented on ODE-262:
-------------------------------------------

To answer Matthieu's comment, yes, the "unique" attribute is better off being declared in the correlation set definition, especially since a correlation set can never ever be initialized more than once. Furthermore, it would be nice to have a "durable" attribute in the correlation set declaration that says whether or not the correlation set has to be unique across all instances, both active and completed. To recapitulate, the revised extensions are as shown below:

<correlationSet name="name"  properties="bar foo ..." unique="yes|no" durable="yes|no"/>

> Duplicated correlation set values is accepted and creates a second instance instead of throwing an exception
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ODE-262
>                 URL: https://issues.apache.org/jira/browse/ODE-262
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.1.1
>         Environment: Apache ODE 1.1.1 or 1.2
> Tomcat
> The counter example of infoq.
>            Reporter: Amin Anjomshoaa
>            Assignee: Karthick Sankarachary
>             Fix For: 2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The classical counter example of infoq (http://www.infoq.com/articles/paul-brown-ode) can be used. Sending the "init" message for the second (third, fourth, ... ) time with the value "foo" will create a new instance. I was expecting a CorrelationViolation exception when the second init message is arriving.
> All upcoming messages are then correlated with the last instance only. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.