[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue - 300 - Proposal for Vote
-1
I would expect a "MUST be omitted" for an empty WSDL message and <fromPart>
or <toPart>. Otherwise, what would you have for the <fromPart> or <toPart>?
It's probably best to leave the text as is. Another option would be to add a
normative MUST preventing the use of <fromPart> or <toPart> with empty
messages. If we do this, it should be added to the static analysis table.
-----Original Message-----
From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]
Sent: Thursday, June 15, 2006 11:05 AM
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] Issue - 300 - Proposal for Vote
Resending the submitter's proposal with proper subject line ...
Explanation: for message activities with empty WSDL messages (no parts), one
may omit the variable attribute -- this clarification adds that
fromPart/toPart may be omitted as well.
Submitter's proposal:
In section 10.3 change the third paragraph from:
"One-way invocation requires only the inputVariable (or its
equivalent <toPart>’s) since a response is not expected as part of
the operation (see section 10.4. Providing Web Service Operations –
Receive). Request-response invocation requires both an inputVariable
(or its equivalent <toPart>’s) and an outputVariable (or its
equivalent <fromPart>’s). If a WSDL message definition does not
contain any parts, then the associated variable attribute,
inputVariable or outputVariable, MAY be omitted. Zero or more
correlationSets can be specified to correlate the business process
instance with a stateful service at the partner’s side (see section
9. Correlation)."
to:
"One-way invocation requires only the inputVariable (or its
equivalent <toPart>’s) since a response is not expected as part of
the operation (see section 10.4. Providing Web Service Operations –
Receive). Request-response invocation requires both an inputVariable
(or its equivalent <toPart>’s) and an outputVariable (or its
equivalent <fromPart>’s). If a WSDL message definition does not
contain any parts, then the associated attributes variable,
inputVariable or outputVariable, or the associated <fromParts> or
<toParts> elements, MAY be omitted. Zero or more correlationSets can
be specified to correlate the business process instance with a
stateful service at the partner’s side (see section 9. Correlation)."
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
----- Forwarded by Dieter Koenig1/Germany/IBM on 15.06.2006 16:59 -----
ws-bpel issues
list editor
<peter.furniss@er To
ebor.co.uk> wsbpel@lists.oasis-open.org
cc
12.06.2006 23:55
Subject
[wsbpel] Issue - 300 - Can
Please respond to <fromParts> and <toParts> be
wsbpel@lists.oasi omitted if WSDL message definition
s-open.org does not contain any parts?
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 - 300 - Can <fromParts> and <toParts> be omitted if WSDL message
definition does not contain any parts?
Status: received
Date added: 12 Jun 2006
Date submitted: 12 June 2006
Submitter: Thomas Schulze
Document: WS-BPEL 2.0 Committee Draft, section 10.3.
Description: The third paragraph in 10.3 is about WSDL messages without
parts. It clarifies that the attributes variable, inputVariable and
outputVariable MAY be omitted but it does not say if <fromParts> and
<toParts> can be omitted for that case.
Submitter's proposal:
In section 10.3 change the third paragraph from:
"One-way invocation requires only the inputVariable (or its
equivalent <toPart>’s) since a response is not expected as part of
the operation (see section Error! Reference source not found.).
Request-response invocation requires both an inputVariable (or its
equivalent <toPart>’s) and an outputVariable (or its equivalent
<fromPart>’s). If a WSDL message definition does not contain any
parts, then the associated variable attribute, inputVariable or
outputVariable, MAY be omitted. Zero or more correlationSets can be
specified to correlate the business process instance with a stateful
service at the partner’s side (see section Error! Reference source
not found.)."
to:
"One-way invocation requires only the inputVariable (or its
equivalent <toPart>’s) since a response is not expected as part of
the operation (see section Error! Reference source not found.).
Request-response invocation requires both an inputVariable (or its
equivalent <toPart>’s) and an outputVariable (or its equivalent
<fromPart>’s). If a WSDL message definition does not contain any
parts, then the associated attributes variable, inputVariable or
outputVariable, or the associated <fromParts> or <toParts> elements,
MAY be omitted. Zero or more correlationSets can be specified to
correlate the business process instance with a stateful service at
the partner’s side (see section Error! Reference source not found.)."
Changes: 12 Jun 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 - 300 -
[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
- 300 - 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).
--------------------------------------------------------------------- To
unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. You may a link to this group and all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]