- From: Assaf Arkin <arkin@intalio.com>
- Date: Wed, 21 May 2003 10:21:34 -0700
- To: Jean-Jacques Dubray <jjd@eigner.com>
- CC: "'Yaron Y. Goland'" <ygoland@bea.com>, "'Burdett, David'" <david.burdett@commerceone.com>, Daniel_Austin@grainger.com, public-ws-chor@w3.org
What about the alternative of binding the BPSS to WSDL, like:
<wsdl:binding ...>
<wsdl:operation ...>
<bpss:transaction name="..." role="..." .../>
</wsdl:operation>
</wsdl:binding>
You already have the binding framework which is used with a variety of
protocols including SOAP, HTTP, IIOP, etc, with a variety of componet
access (see WSIF), and so forth. So instead of reinventing all these
bindings in WS Choreo, how about we just add another binding to WSDL to
address BPSS transactions?
arkin
Jean-Jacques Dubray wrote:
>The cost of abstraction is way overestimated here. The abstraction is
>already built, it is called a message and a message exchange pattern.
>Now we have the choice to directly use the WSDL message definition or
>rather define something like:
>
><message name="ProcessPO">
><message name="AckPO>
><mep name="ProcessPO">
>
><binding message="ProcessPO" type="WSDL" version="1.2">
> <portType="">
></binding>
><binding MEP="ProcessPO" type="ebXML" version="2.0>
> <BPSS
>URI=http://oasis.org/bunchOfStandardsCollabs/aPOCollaboration">
> <businessTransactionActivity name="ProcessPO>
></binding>
><binding message="AckPO" type="PlainOldFax" >
> <fax number="555-1234"/>
></binding>
>
>so please, let's reasonable on our assertions.
>
>I am currently on travel in beautiful Berlin, with limited email and web
>access. So I will respond more thoroughly to the emails this week-end.
>
>Cheers,
>
>JJ-
>
Received on Wednesday, 21 May 2003 13:25:07 UTC