Re: [sca-bpel] Issue 57: proposal

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

No worries.
Will try to send things out earlier, but gets harder given our 
deadline-driven lives. In any case, you should feel free to object to 
resolving issues whose proposals you haven't seen 24/48 hours in 
advance. The chairs would certainly be sympathetic to such a request.

In any case, I think we did have a good discussion on the (0..1) case 
and idempotent case.

-Anish
--

On 11/5/2009 11:14 AM, Danny van der Rijn wrote:
> Apologies for derailing the discussion on the call today.  I would say 
> in my defense, however, that I hadn't had a chance to see the proposal 
> before the call.  I'm standing on thin ice here, joining the call late, 
> and from my car, but it would help greatly to defer discussion of 
> proposals until at least 24 hours from the time they were sent.  48 
> hours would be better...
> 
> On 11/4/2009 10:02 PM, Anish Karmarkar wrote:
>>
>> Issue 57 (http://osoa.org/jira/browse/BPEL-57) says:
>>
>> "Variable with sca-bpel:multiReference extension needs to be
>> initialized/Set before it can be used to set the partner link endpoint
>> reference. Specification does not say anything about variable
>> initialization mechanism."
>>
>> This issue was raised before some of the recent changes to the spec.
>> Specifically the issue proposal from Najeeb that was accepted recently.
>> The spec (cd02-rev4) says the following in Section 3.2:
>>
>> "Variable 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."
>>
>> Given this statement in the spec, I think we can CNA this issue.
>>
>> -Anish
>> --
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>