[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] issue 168
Diane, Words like <receive> and <pick> have been dropped from the option 2 description (probably through HTML editing?). Yuzo Fujishima NEC Corporation Diane Jordan wrote: > On the last TC call, the folks who proposed alternatives for resolving > issue 168 requested more input either by email or in the calls. We > decided to open a web ballot and hope that would serve to focus attention > on the choices - a discussion of 168 will be on the agenda for our call > next week. The ballot will close after the call and votes may be changed > up to closing time. If you have input on the issue or proposed > resolutions, please feel free to provide them by email beforehand to help > stimulate the thinking and discussion. > You may vote at: > http://www.oasis-open.org/apps/org/workgroup/wsbpel/ballot.php?id=600& > > Here is the text of the ballot: > Please chose one option for closing issue 168 > 1. We should guarantee that an initial start activity will complete before > any other activities are allowed to execute. This will prevent race > conditions, prevent us from having to discuss the dispatcher, prevent a > bunch of edge cases and make sure that the existing event handler model > will work just fine. See email with full info at: > http://lists.oasis-open.org/archives/wsbpel/200411/msg00018.html > > 2. 2 Adopt the "less magic" approach described in the issue description. > This means that the semantics of process instantiation would be as > follows: > 1. The arrival of message that matches an activity marked with > createInstance=yes (and not matching an existing process instance) causes > a new process instance to be created. This message is termed the > "instantiating message" for that process instance. The createInstance=yes > activity that was used to justify the instantiation is termed the > "instantiating activity" for that process instance. > 2. Once a process instance is created, all its activities are executed in > the order dictated by the structure of the process. > 3. When a or activity with createInstance=yes containing a initiate=yes > correlation is executed, the message "received" will be the "instantiating > message" of the process instance. > 4. When a and activity with createInstance=yes containing a > initiate=rendezvous correlation is executed, the message "received" will > be either: > a ) the "instantiating message" if said activity is the "instantiating > activity" > b ) some other message matching the correlation key from the > "instantiating message" if said activity is not the "instantiating > activity" > > See email for full info at : > http://lists.oasis-open.org/archives/wsbpel/200410/msg00167.html > > Regards, Diane > IBM Emerging Internet Software Standards > drj@us.ibm.com > (919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709 >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]