OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [wsbpel] Issue - 37 - Initiating Correlation Set More Than Once

After thinking about this again, my opinion is that we should stick with the intent of the original authors.  I recognize the similarity with the multiple start activities but there is also a crucial difference.  In the case of multiple start activities, the multiple initiations of the correlation are unavoidable since there is no other way to achieve the rendezvous of the multiple non-deterministically ordered activation messages.  In the cases where instance creation is not involved, there must already be a known correlation for the message to be delivered to the instance and hence it is not a case of rendezvous-by-correlation.  I cannot think of real examples where multiple initiations of a correlation set would be meaningful other than in the multiple start activities case.  I therefore have to agree with Yaron that this is most likely to arise as a process design error.


From: Yuzo Fujishima [mailto:fujishima@bc.jp.nec.com]
Sent: Sat 9/27/2003 2:02 AM
To: wsbpel@lists.oasis-open.org
Subject: Re: [wsbpel] Issue - 37 - Initiating Correlation Set More Than Once


Here is my summary of our discussion on Issue 37 at the last F2F meeting:

Issue 37: What will happen if a correlation set is initiated more than once
                 during the lifetime of the corresponding scope?

The intent of the original authors was (Satish)
A) bpws:correlationViolation fault is always thrown
      -- for executable processes and the situation is marked as "undefined"
         for abstract processes.

My comment was:
  A is somewhat incompatible with the interpreation of the Mulitple Start Activities
  example described in the specification document.

My proposal was:
B) References to already initialized correlation set are treated as if initiate="no"
     regardless of the specified value.
     -- Only for start activities. (This line was added today.)

Danny's proposal/comment: (Please correct if wrong)
C) We may introduce an attribute value initiate="yesIfNotYet" or the like.

Somebody's proposal/comment (Sorry I forgot who)(Please correct if wrong)
D) Remove initiate attribute completely. Correlation sets are initialized
     at the first use.

Yaron's comment: (Please correct if wrong)
   Tolerating multiple initialization may raise the possibility of the user's
   making inadvertent mistakes.

Yuzo Fujishima
NEC Corporation

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]