On 2/28/07, Jiang Liu <[EMAIL PROTECTED]> 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
