Issues 87.1 and 168 resolved

[Diane Jordan <drj@us.ibm.com>]

In case you missed the results
of the web ballots for 168 and 87.1, here they are:  
Issue 87.1 resolution:

The WS-BPEL TC should standardize in BPEL the way to access and set application data (as defined in WSDL 2.0).	10	29
Close with no change to the spec. The WS-BPEL TC should not standardize a way to use WSDL 1.1 web services in BPEL with the WSDL 2.0 extension for application data.	22	65
Abstain	2	6

Eligible members who have voted:

34 of 45

76%

Issue 168 resolution:

Option	# Votes	% of Total
option 1	29	88
option 2	4	12
abstain	0	0

Eligible members who have voted:

33 of 45

73%

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