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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bpel message

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


Subject: NEW ISSUE: Title: Need to deal with variable initialization not beingidempotent


TARGET: SCA C+I WS-BPEL spec, General

DESCRIPTION:
 
WS-BPEL section 8.1 contains the following requirement:

[SA00026] Variable initialization logic contained in scopes that contain or whose children contain a start activity MUST only use idempotent functions in the from-spec. The use of idempotent functions allows for all the values for such variables to be pre-computed and re-used on each process instance.

SCA-BPEL 3.2 (CD02-rev4) has the following new text

Variable (sic) with “sca-bpel:multiReference” extension is initialized by sca runtime using an implicit <from-spec> that uses an expression that  points to a virtual sca runtime variable holding a list of endpoint references for the targets of the multi-reference represented by a partner link referencing this variable. 


Which is in conflict with WS-BPEL SA00026.  Similarly, but not as precisely, SCA-BPEL 3.1 describes how properties are initialized, and that section runs afoul of the same statement.

PROPOSAL: none

S/MIME Cryptographic Signature



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