[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] RE: Issue - 77 - Motion to require access to values not defined in portType
Here is my proposal for a resolution of this issue: Allow multiple abstract messages to be associated with each input and output variable in those activities (invoke, receive, reply) where only a single abstract message is currently allowed. Ugo > -----Original Message----- > From: Ugo Corda > Sent: Sunday, November 02, 2003 11:14 AM > To: wsbpel@lists.oasis-open.org > Subject: RE: [wsbpel] RE: Issue - 77 - Motion to require access to > values not defined in portType > > > Reformulation of the issue: > > Given the fact that a few people are bothered by mentioning > SOAP and SOAP headers, let me try to reformulate the issue > exclusively in terms of abstract interface. Here it goes. > > WSDL 1.1 can define various abstract messages as part of its > abstract interface. Some of these messages show up in > abstract WSDL operations, some others don't. BPEL can only > process abstract messages that are part of WSDL operations, > and it cannot process any other abstract message. What is the > rationale for that? > > Ugo > > To unsubscribe from this mailing list (and be removed from > the roster of the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/le ave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]