atom feed19 messages in org.oasis-open.lists.wsbpelRe: [wsbpel] inputVariable optional o...
FromSent OnAttachments
Yaron Y. GolandJul 16, 2004 9:59 am 
Ron Ten-HoveJul 16, 2004 11:25 am 
Prasad YendluriJul 16, 2004 12:16 pm 
Ugo CordaJul 16, 2004 1:28 pm 
Ron Ten-HoveJul 16, 2004 2:40 pm 
Prasad YendluriJul 16, 2004 4:20 pm 
Prasad YendluriJul 16, 2004 4:28 pm 
Ugo CordaJul 16, 2004 4:35 pm 
Prasad YendluriJul 16, 2004 4:49 pm 
Ugo CordaJul 16, 2004 5:02 pm 
Danny van der RijnJul 16, 2004 5:05 pm 
Danny van der RijnJul 16, 2004 5:06 pm 
Prasad YendluriJul 16, 2004 5:12 pm 
Prasad YendluriJul 16, 2004 5:19 pm 
Ron Ten-HoveJul 16, 2004 5:35 pm 
Yaron Y. GolandJul 19, 2004 10:18 am 
Prasad YendluriJul 19, 2004 11:29 am 
Yaron Y. GolandJul 20, 2004 10:07 am 
Monica J. MartinJul 20, 2004 10:24 am 
Subject:Re: [wsbpel] inputVariable optional on Invoke
From:Prasad Yendluri (pyen@webmethods.com)
Date:Jul 16, 2004 5:12:59 pm
List:org.oasis-open.lists.wsbpel

That is permitted for MEPs with no input (E.g. Notification from the server) and not for request/response MEPs, which is all we have in BPEL.

Ugo Corda wrote:

> Additionally WSDL 2.0 replaces messages with GEDs which can be empty as well.

Yes, but in WSDL 2.0 the reference to GEDs is optional within the operation description. From that point of view, making our variable optional would in a way capture the direction where WSDL is going..

Ugo