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: [ISSUE 64]: Name of the generated SCA reference for a partnerLinkdeclared with multiRefFrom extension


This is issue 64.
http://osoa.org/jira/browse/BPEL-64

-Anish
--

On 8/18/2010 10:14 AM, Patil, Sanjay wrote:
> Title: Name of the generated SCA reference for a partnerLink declared
> with multiRefFrom extension
> Target: SCA WS-BPEL C&I Specification Version 1.1 CD 2 Rev 9
> Description:
> There is no normative statement in the specification for generating name
> of an SCA reference which corresponds to a partnerLink that uses the
> multiRefFrom extension.
> There is discrepancy in how the name of a reference is generated for a
> partnerLink with multiRefFrom extension:
>
>     * Section 2.3.1 uses the name of the variable with multiReference
>       extension as the name of the generated reference. See the text:
>       ‘Else if the name attribute is present on the
>       sca-bpel:multiReference extension …’
>     * Section 3.2 uses the name of the partnerLink as the name of the
>       generated reference. See the text at the bottom of the section: ‘A
>       multi-value reference named “vendorLink” , which his categorized as …”
>
> Proposal:
> Add a normative statement after the SBPEL2024 statement: The name of the
> reference MUST be the value of the name attribute of the partnerLink.
> Update the sections 2.3.1 and 3.2 to comply with the added normative
> statement.


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