[ https://issues.apache.org/jira/browse/ODE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthick Sankarachary updated ODE-262:
--------------------------------------
Summary: Treating Duplicate Correlation Set Values (was: Duplicated correlation set values
is accepted and creates a second instance instead of throwing an exception)
> Treating Duplicate Correlation Set Values
> -----------------------------------------
>
> 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.
|