[
https://issues.apache.org/jira/browse/ODE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthick Sankarachary updated ODE-478:
--------------------------------------
Attachment: correlation-consistency-constraint.patch
> Observe Correlation Consistency Constraint On Initiate
> ------------------------------------------------------
>
> Key: ODE-478
> URL: https://issues.apache.org/jira/browse/ODE-478
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3
> Environment: platform-independent
> Reporter: Karthick Sankarachary
> Fix For: 1.3
>
> Attachments: correlation-consistency-constraint.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> The "correlation consistency constraint" mandates that if a correlation set,
> whose initiate attribute is set to "yes", is already initiated, then the
> standard fault bpel:correlationViolation MUST be thrown.
> Right now, the server simply ignores that violation and moves the process
> forward as if nothing is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
