RE: [wsbpel] RE: Issue - 77 - Motion to require access to values not defined in portType

["Satish Thatte" <satisht@microsoft.com>]

Ugo,
 
Let us state clearly the current relationship between BPEL and WSDL interfaces.
 
BPEL allows Web service *operations* defined by such interfaces to be invoked or provided by BPEL processes.  Messages occur in these interactions only in so far as they participate in the definition of the operations in the concerned portType.
 
Your proposal suggests that we change this fundamental design point, and start dealing with messages independent of their association with operations in a portType.  Do you agree?  Is there any constraint you have in mind for which message types would be associated with the input and output variables for web service interactions?
 
Satish

________________________________

From: Ugo Corda [mailto:UCorda@SeeBeyond.com]
Sent: Mon 11/3/2003 8:26 AM
To: wsbpel@lists.oasis-open.org
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.


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/leave_workgroup.php.