You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ode.apache.org by "Karthick Sankarachary (JIRA)" <ji...@apache.org> on 2009/04/17 22:22:15 UTC

[jira] Closed: (ODE-478) Observe Correlation Consistency Constraint On Initiate

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

Karthick Sankarachary closed ODE-478.
-------------------------------------


> 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.1
>         Environment: platform-independent
>            Reporter: Karthick Sankarachary
>            Assignee: Karthick Sankarachary
>             Fix For: 1.3.1
>
>         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.