ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (ODE-262) Duplicated correlation set values is accepted and creates a second instance instead of throwing an exception
Date Fri, 19 Dec 2008 21:40:45 GMT

    [ https://issues.apache.org/jira/browse/ODE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658190#action_12658190
] 

boisvert edited comment on ODE-262 at 12/19/08 1:39 PM:
-------------------------------------------------------------

Karthick, does this change in any way the persistence of process definitions, instances or
any other persistent object in Ode?  (I can't easily tell from the commit because of the changes
in line-ending characters).   And if so, are the changes backward-compatible?

      was (Author: boisvert):
    Karthick, does this change in any way the persistence of process definitions, instances
or any other persistent object in Ode?  (I can't easily tell from the commit because of the
changes in line-ending characters)
  
> 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
>
>   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