Guillaume, In an ideal message-oriented world I would agree that the EPR would encapsulate the operation. However, in reality this is not the case: most often an EPR amounts to a URL, and a SOAPAction field is required to specify an operation. This state of affairs is implicitly encoded in the BPEL specification: you can assign an "EPR" to a partner link, and then separately select an operation to invoke on that EPR. -mbs
On Wed, 2006-05-31 at 08:55 +0200, Guillaume Nodet wrote: > And I still do not understand why the operation name is the only > attribute available > on message exchange. Either put all attributes in the EPR or put all > available > attributes on the exchange (imho we should at least have the PortType > QName). > > Cheers, > Guillaume Nodet > > > > > Lance > > > > On 5/25/06, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > >> > >> Hi all, > >> > >> I've just imported the revised version of the integration API > >> specified by Maciej (if somebody with the necessary karma reads this, > >> Maciej's CLA has been received but he's the last one without an > >> account) for review. He also brushed up the javadoc. > >> > >> Comments are welcome (even just to say "Good job Maciej!" :-) ). > >> > >> Cheers, > >> > >> Matthieu. > >> > >
