ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: Re: Re: Re: Asynchronous service invocation question
Date Thu, 01 Mar 2007 18:40:15 GMT
On 2/28/07, Jiang Liu <S3075163@student.rmit.edu.au> wrote:
>
> For static, for example, say in my consumer service WSDL, the callback
> protType is defined as "myRole" in partner links definitions, which means
> consumer is not responsable for implementing this "callback" portType in its
> skeleton, its BPEL's responsibility.
>
> BPEL implements it by adding a <receive> to create a thread listening to
> it; on the other hand, consumer only implements "partnerRole" portTypes. Say
> if i have a "call" partnerRole in consumer side, when consumer receives
> message from BPEL, it starts processing the message. After a "long" while,
> the process is done, then what? Because in consumer's skeleton, it only
> implements "call" not "callback".



Jiang, could you provide an example of the interaction you have in mind?
(BPEL pseudocode would work)  It would help me better understand what you're
trying to do.

alex

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