wsbpel message

Subject: Issue - 148 - Explicitly state that solicit/response & notification aren't supported by BPEL

From: ws-bpel issues list editor<peter.furniss@choreology.com>
To: wsbpel@lists.oasis-open.org
Date: Sat, 17 Jul 2004 14:45:09 +0100

This issue has been added to the wsbpel 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 - 148 - Explicitly state that solicit/response & notification aren't supported by BPEL

Status: open
Categories: Specification editing
Date added: 17 Jul 2004
Submitter: Yaron Y. Goland
Date submitted: 16 July 2004
Description: There is an explicit assumption in the BPEL spec that solicit/response and notification WSDL MEPs are not supported by BPEL. We need to make this assumption explicit.

What isn't clear is what we should do if someone gives us a WSDL with a solicit/response or notification. Should we ignore it? Should we throw an error? If only one role in a partnerLink has a WSDL should we transmute the solicit/response or notification on that WSDL into a mirror image WSDL for the other role using request/response or one way? What if both roles have a fully specified WSDL? In that case should we validate that the solicit/response or notification on one role's WSDL is matched with a request/response or one way on the other role's WSDL? If there isn't a matching pair should we create a match on the other role's WSDL?
Submitter's proposal: I suspect the simplest and most robust solution is that if BPEL is given a WSDL with a solicit/response or notification then an error MUST be thrown. I don't like ignoring things in cases like this, it causes confusion. If a tool wants to be really smart and do pre-processing to turn solicit/response or notification into a mirror image WSDL that's fine but it's also out of scope for BPEL. I think that all BPEL should care about is that when the WSDLs are submitted they don't have any solicit/response or notification operations.
Changes: 17 Jul 2004 - new issue

To comment on this issue, 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 - 148 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 148 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).