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 218 - Proposal for vote


Hi all,

Below is the spec text capturing my resolution for Issue 218 with the amendments we discussed today at the conf call:

Proposed Spec Text Changes to resolve Issue 218
In Section 12.6, after paragraph 1:
Add: The same isolation semantics apply to properties, being merely projections of variables and thus always coupled with them; access to properties is identical to access to variables, which is controlled by the isolated scope.
In Section 12.6, after paragraph 3:
Add: Any partnerLinks referenced within an isolated scope have their access protected by that scope; the protection applies specifically to the endpointReference part, and not the messageExchange parts, of the partnerLink state. Any messageExchange referenced in a scope serves only to provide a handle to access a facet of the state of its associated partnerLink; it is intrinsically stateless. The control afforded by the isolated scope does not apply to messageExchange handles. Rather, partnerLink states are protected based on the endpointReference. 
By definition, correlation sets are only mutable at initialization; they are immutable throughout the remainder of their lifecycle. Any correlation sets referenced within an isolated scope do not have their access controlled by that scope. However, the initialization of a correlation set is performed in an atomic fashion - in the same sense as that of an <assign> operation - ensuring that the correlation set will only be initialized once - wholly, and never partially.

Cheers,

-Charlton.
--
Adobe Systems Incorporated
+1 (408) 536-4496 p
cbarreto@adobe.com


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