The pattern for this in BPEL would be to have an invoke to the long running service followed by a receive or pick activity for the callback. The message to the service should contain the addressing information for the callback within the header or body along with some correlating properties.
I don¹t know if ODE fully supports WS-Addressing such that it would auto-populate the ReplyTo in the SOAP message but there is an extension in ODE for reading and writing message headers that may be of some use to you: http://ode.apache.org/headers-handling.html On 10/2/09 8:53 AM, "Michael Dondrup" <[email protected]> wrote: > Dear ODE list, > > I have a question regarding asynchronous transport message exchange > pattern using WS-addressing. > This might be even a more a general BPEL question but I would like to > know if and how this is possible with ODE 2. Here's the use-case > > I have a long running (> 5 min) SOAP service having a single > computational operation (BLATquery). The service supports WS- > Addressing (via Axis2 1.5). When I try to consume the service using an > Axis 2 client, I pass it a ReplyTo EPR. Axis2 then starts up a > simpleHTTP server on port 6060, waiting for the reply on this EPR. > This works by sending the request and response in two http connections > and therefore there is no transport timeout. > > Can I mimic this behaviour using a BPEL process without having to add > a Start and End method to the service or change it otherwise? I came > accross this page > http://ode.apache.org/endpoint-references.html > but I couldn't figure out how to exploit this for my case. > I attach the wsdl file of the service for reference (I have made a > process also, but as it doesn't seem to work it would just cause > confusion). > Any help or example would be appreciated, or do I do something > conceptually wrong? > > Thank you > Michael > > -- Mark Ford MIT Lincoln Laboratory 244 Wood Street Lexington MA 02420 (781) 981-1843
smime.p7s
Description: S/MIME cryptographic signature
