[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue - R24 - Externally referenced locally-scopedpartnerLinks
Dieter Koenig1 wrote: > The WS-BPEL specification does not standardize external references to > partner links or other elements. Moreover, it is out of scope how partner > links are bound. > +1 I would prefer that any public response to the question not muddy the question with the below response. > One could imagine e.g. using XPath expressions for uniquely identifying > constructs within a WS-BPEL process definition. Naturally, this does not > consider runtime aspects. Scopes with local partner links may be embedded > in repeatable constructs (loops or event handlers) where partner links > inside each scope instance may have to be treated individually. > > For the purpose of binding WS-BPEL partner links to external entities, see > also the papers produced by the Open Service Oriented Architecture > collaboration (osoa.org), in particular the Service Component Architecture > (SCA) Client and Implementation Model for BPEL (at > http://osoa.org/download/attachments/35/SCA_ClientAndImplementationModelforBPEL_v0.95.pdf?version=2) > which specifies the binding of WS-BPEL partner links within an SCA > component assembly and also addresses scoped partner links (in section > 1.3.3). > > HTH > Kind Regards > DK > > Dieter König Mail: dieterkoenig@de.ibm.com IBM Deutschland Entwicklung GmbH > > Senior Technical Staff Member Tel (office): (+49) 7031-16-3426 Schönaicher Strasse 220 > > Architect, Business Process Choreographer Fax (office): (+49) 7031-16-4890 71032 Böblingen > > Member, Technical Expert Council Tel (home office): (+49) 7032-201464 Germany > > > > > > > > ws-bpel issues > list editor > <peter@furniss.co To > .uk> wsbpel@lists.oasis-open.org > cc > 18.10.2006 01:13 > Subject > [wsbpel] Issue - R24 - Externally > Please respond to referenced locally-scoped > wsbpel@lists.oasi partnerLinks > s-open.org > > > > > > > > > > This issue has been added to the wsbpel issue list with a status of > "received". The status will be changed to "open" if a motion to open the > issue is proposed and that motion is approved by the TC. A motion could > also be proposed to close it without further consideration. Otherwise it > will remain as "received". > > > The issues list is posted as a Technical Committee document to the OASIS > WSBPEL TC pages on a regular basis. The current edition, as a TC document, > is the most recent version of the document entitled in the "Issues" folder > of the WSBPEL TC document list - the next posting as a TC document will > include this issue. The list editor's working copy, which will normally > include an issue when it is announced, is available at this constant URL. > Issue - R24 - Externally referenced locally-scoped partnerLinks > > > Status: received > Date added: 17 Oct 2006 > Origin: Public comment - Jim Clunes, 16 October 2006 > Date submitted: 17 October 2006 > Description: Is there a standard way to refer to a locally-scoped > partnerLink from outside the process? My reading of the specification is > that partnerLink names need only be unique within the scope that they are > defined, not necessarily unique to the entire process. > > > However, the last sentence of section 6.2 says: > The initial binding information of a <partnerLink> can be set as a > part of business process deployment, regardless of whether it is > declared on the <process> or <scope> element level. > > > What identifier should deployment descriptors use to reference these > locally-scoped partnerLinks for the purpose of initializePartnerRole? > Changes: 17 Oct 2006 - new issue > > > > To comment on this issue (including whether it should be accepted), please > follow-up to this announcement on the wsbpel@lists.oasis-open.org list > (replying to this message should automatically send your message to that > list), or ensure the subject line as you send it starts "Issue - R24 - > [anything]" or is a reply to such a message. If you want to formally > propose a resolution to an open issue, please start the subject line "Issue > - R24 - Proposed resolution", without any Re: or similar. > > > To add a new issue, see the issues procedures document > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]