ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matth...@offthelip.org>
Subject Re: Stateful Exchange Protocol/-Headers
Date Tue, 27 May 2008 18:50:52 GMT
On Tue, May 27, 2008 at 12:34 AM, Matthias Füller <matthias.fueller@gmx.net>
wrote:

> Hi!
>
> I didnt find a solution for apache ODE. So I tried activeBPELwith its
> "engine managed correlation". And it works fine. I can select the
> process-instance via the soap header.
>
> I?m looking for a similar solution for apache ODE. Can anybody help me?
>

Sorry I seem to have missed your first message somehow. I remember looking
at it though, I probably got sidetracked. Anyway, I'll try to help. The
headers we send and receive look like:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
">
    <SOAP-ENV:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:sess="http://www.intalio.com/type/session">
        <wsa:To>
            <wsa:Address>http://address.to.target.service</wsa:Address>
            <sess:session>XYZ</sess:session>
        </wsa:To>
        <sess:callback>
            <wsa:Address>http://my.callback.address</wsa:Address>
            <sess:session>ABC</sess:session>
        </sess:callback>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        ....
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

A process will always send its own endpoint in the callback header if it
expects to be called later on (in BPEL terms, if the corresponding partner
link has a myRole). Conversely, when a process is invoked, it will always
store the callback address of a partner so that it can provide it later on
when invoking that partner. It will also route to the correct instance if
you provide a session in the wsa:to header.

Does that help?

Cheers,
Matthieu

P.S. I just realized when writing this e-mail that we just have one Intalio
namespace hanging there. We'll have to update that.


>
> regards
> Matthias
>
> Matthias Füller schrieb:
>
>  Hello!
>>
>> I am looking for a method where several non-ODE services can "talk" to the
>> same BPEL-instance without using correlation sets.
>> So ODEs stateful exchange protocol looks like a good solution for my
>> problem.
>>
>> If I unstand the stateful mechanism right, I can refer the instances over
>> ws-adressing (and its reference properties) or directly in the soap-header.
>> But I have some questions on the stateful exchange protocol:
>> - What is the namespace of the the <state:identifier>- or
>> <state:use>-elements (explaind on point 7 at
>> http://ode.apache.org/stateful-exchange-protocol.html )?
>> - Is it possible to select an instance via the process-instance-id or will
>> ODE generate its own key?
>> - Can someone provide a small example of the soap-message for the SEP?
>>
>> thanks a lot
>> Matthias
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message