ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthick Sankarachary (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-262) Duplicated correlation set values is accepted and creates a second instance instead of throwing an exception
Date Fri, 09 Jan 2009 01:52:59 GMT

     [ https://issues.apache.org/jira/browse/ODE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karthick Sankarachary updated ODE-262:
--------------------------------------

    Attachment: unique-correlation-set-non-instantiating.patch

On second thought, the constraint of uniqueness of correlation sets should be enforced on
not only instantiating receives, but also intermediate receives and for that matter, any inbound
or outbound message activity in which a correlation set may potentially be initialized, such
as a <reply>, <invoke>, <pick> or <onEvent> activity.

The patch that goes with this comment accomplishes just that.

> 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
>
>         Attachments: unique-correlation-set-for-branch.patch, unique-correlation-set-for-trunk.patch,
unique-correlation-set-non-instantiating.patch
>
>   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.


Mime
View raw message