Also the standard method to handle the callback necessity is correlation. It's not really a callback mechanism per se but it allows the engine to route correctly a service callback.
Matthieu On 2/28/07, Alex Boisvert <[EMAIL PROTECTED]> wrote:
On 2/28/07, Jiang Liu <[EMAIL PROTECTED]> wrote: > > Hi Jim > Really thanks for your quick reply. I did read somewhere that said > WS-Addressing is utilized here, but for WSDL2, is still? > > And the main problem is since the external service does not have to > implement "callback" logic, so even it got BPEL's EPR, how does it know when > is the best time to send reply back? As soon as you have a callback EPR, you should be able to invoke it. Now whether it works in practice is a question of message exchange pattern and transport layer. Ode queues all messages it receives, so if you have a one-way invocation, or a request-response invocation happening over a connection-less protocol (e.g. JMS) then it should work. The message will be queued and processed when the process reaches the corresponding <receive> activity. For the HTTP protocol, you have to stick to one-way invocations to avoid transport-level timeouts. alex
