RE: [wsbpel] Possible new issue: BPEL cannot handle some SOAP header bindings

["Ugo Corda" <UCorda@SeeBeyond.com>]

Frank,

Sure it is related to binding. But, if you remember, one of our major concerns regarding BP 1.0 compliance was that it would prevent BPEL from interacting with existing Web services (those that had bindings other than SOAP/HTTP).

So, if we are so concerned about supporting existing Web services when it comes to BP 1.0 compliance, I don't see why we should not be concerned about BPEL not being able to interact with a whole category of existing Web services because of a language limitation in the way variables are defined in association with various BPEL operations.

Ugo

> -----Original Message-----
> From: Frank Leymann [mailto:LEY1@de.ibm.com]
> Sent: Tuesday, October 21, 2003 1:05 AM
> To: wsbpel@lists.oasis-open.org
> Subject: Re: [wsbpel] Possible new issue: BPEL cannot handle some SOAP
> header bindings
> 
> 
> 
> Ugo,  this is a deployment/binding issue that is not 
> addressed by BPEL at
> all. You easily write down bindings that won't work with a 
> certain BPEL
> process model...
> 
> Regards,
> Frank
> 
> 
> 
> 
> 
> 
> 
> To:    <wsbpel@lists.oasis-open.org>
> cc:
> Subject:    [wsbpel] Possible new issue: BPEL cannot handle some SOAP
>        header bindings
> 
> 
> Let's suppose we have the following WSDL file:
> 
> 
> <message name="In">
>     <part name="InPart" element="InElement"/>
> </message>
> 
> 
> <message name="Header">
>     <part name="HeaderPart" element="HeaderElement"/>
> </message>
> 
> 
> <portType name="myPortType">
>     <operation name="op1">
>         <input message="In"/>
>     </operation>
> </portType>
> 
> 
> <binding type="myPortType" ... >
>     <soap:binding ..../>
>     <operation name="op1">
>         <input>
>             <soap:body parts="InPart" ...>
>             <soap:header message="Header" part="HeaderPart" .../>
>         </input>
>     </operation>
> </binding>
> 
> 
> In this example, the abstract operation "op1" refers to 
> message "In", but
> the binding brings in an additional second message, "Header", for the
> concrete operation.
> 
> 
> It seems that BPEL would not be able to process the "Header" 
> information in
> any way. For instance, a "receive" operation would only be 
> able to specify
> one inputVariable, which would be associated with the "In" 
> message and not
> the "Header" message. In other words, the "Header" message would carry
> information to the "receive" operation that BPEL would have 
> no access to.
> 
> 
> If this is the case, new Web services defined with BPEL in mind could
> easily modify this scenario by defining both body and header 
> as being part
> of a single message, but legacy Web services might be out of reach for
> BPEL.
> 
> 
> Please confirm that the current status is as I described. If 
> it is, I will
> formally raise a new issue.
> 
> 
> Thank you,
> 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.