[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-bpel] Proposal for SCA-BPEL Issue 39
Hi Dieter, I think this issue (#39) as well as an earlier (resolved) issue (#31)[1] impact the same statement in the specification. Therefore I think the resolution for issue 39 should be inclusive of the previously adopted resolution for issue 31. If I understand the issue 39 correctly, it can be resolving by updating the resolution of the issue 31 as follows. Change the issue 31 resolution From [SBPEL3011] The partnerLinkType and partnerRole attributes of the <partnerLink> MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable whose @name value is same as the value of the @multiRefFrom attribute of the <partnerLink>. To [SBPEL3011] The partnerLinkType attribute and the partnerRole of the <partnerLink> MUST be the same as the partnerLinkType and partnerRole attributes of the <sca-bpel:multiReference> child element of the variable whose @name value is same as the value of the @multiRefFrom attribute of the <partnerLink>. Comments? -- Sanjay [1] http://www.osoa.org/jira/browse/BPEL-31 > -----Original Message----- > From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com] > Sent: Friday, May 01, 2009 3:28 AM > To: sca-bpel@lists.oasis-open.org > Subject: [sca-bpel] Proposal for SCA-BPEL Issue 39 > > > > We discussed the proposal for SCA-BPEL issue 39 ( > http://www.osoa.org/jira/browse/BPEL-39) during the last TC call. > > After re-checking, I think that the current proposal does not > need to be > revised. > > The proposed new text ... > > [SBPEL3011] The partnerLinkType attribute of the partner link and > multi-valued reference variable MUST be matched and the partnerRole > attribute of the multi-valued reference variable MUST match > the partnerRole > of the partner link. > > ... only refers to the **partnerRole attribute** of the **multi-valued > reference** (which always has the partnerRole attribute) and > refers to the > **partnerRole** of the **partner link** (which may only have > the myRole > attribute specified). > > With that, this rule is consistent with others in referring to the > partnerRole without explicitly requiring the **partnerRole > attribute** to > be present on a **partner link**. > > Let's revisit this in the next call. > > Kind Regards > > Dieter König > > Senior Technical Staff Member, WebSphere Process Server Architect > IBM Software Group, Application and Integration Middleware Software > WSS Business Process Solutions > > > > > > > > > > > Phone: +49-7031-16-3426 IBM > Deutschland (Embedded > > image moved > > to file: > > pic26786.gif) > > > E-Mail: dieterkoenig@de.ibm.com Schönaicher > Str. 220 > > > 71032 > Böblingen > > > Germany > > > > > > > > > > > > IBM Deutschland > > Research & > > Development > > GmbH / > > Vorsitzender des > > Aufsichtsrats: > > Martin Jetter > > Geschäftsführung: > > Erich Baier > > Sitz der > > Gesellschaft: > > Böblingen / > > Registergericht: > > Amtsgericht > > Stuttgart, HRB > > 243294 > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]