Issue - R43 - Simplify partnerLink usage

[ws-bpel issues list editor<peter@furniss.co.uk>]

This issue has been added to the wsbpel issue list with a status of "open". The TC agreed to accept the issue before it was added to the issue list.

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 - R43 - Simplify partnerLink usage

Status: received
Date added: 16 Nov 2006
Date submitted: 16 Nov 2006
Submitter: Charlton Barreto
Description:  This issue was split from - issue R32 in the resolution of that issue.  Some of the message proposing it referred to  issue R29.

(from issue 32, part C Simplify partnerLink usage: Potentially, we can simplify partnerLink usage (not a bug). The number of partnerLink used in this example is a bit too many. It makes the example harder to understand. I would suggest to combine some of them.

• "ordering" + "orderingResponse" + "orderingConfirmation" => "ordering" (initializePartnerRole="no")
• "shipper" + "shipperResponse" => "shipper" (initializePartnerRole="yes")
• "invoiceProcessor" + "invoiceResponse" => "invoiceProcessor" (initializePartnerRole="no")
• "shipperRequester" unchanged (initializePartnerRole="no")

Submitter's proposal: It is proposed that the use of partnerLinks be simplified in Section 15.2, the Template Profile example, by combining the multiple partnerLinks in the example: orderingResponse into ordering, shippingResponse into shipping, and invoiceResponse into invoice, using multiple portTypes and roles to represent the request/response relationships. Also, the use of initializePartnerRole has been updated.
Links: issue R32 : Correction needed in Template Process Example in Section 15.2 
Changes: 16 Nov 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 - R43 - [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 - R43 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document