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] Resolved: (ODE-478) Observe Correlation Consistency Constraint On Initiate
Date Fri, 09 Jan 2009 20:06:00 GMT

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

Karthick Sankarachary resolved ODE-478.

    Resolution: Fixed

A patch that raises a bpel:correlationViolation fault in the event of re-initiations of correlation
sets has been applied. Furthermore, if the message activity that attempts to initiate that
correlation set is a <reply> activity, then the fault is propagated back to the client
in the form of a SOAP fault.

> 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
>            Assignee: 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.

View raw message