Yeah, this is a pattern that imho should be handled by an EIP endpoint which would receive an InOut exchange and send an InOnly request while waiting for an InOnly response. THis component would be responsible for correlating the request and the response, unfortunately it has not been written yet. A jira already exists for this: http://issues.apache.org/activemq/browse/SM-454. Do you want to try implementing it ?
On 2/3/07, MrRothstein <[EMAIL PROTECTED]> wrote:
Hi All, Hoping you guys can point me in the right direction. I'm integrating with an async serivce (one channel for requests and another for replies). The replies will have a correlation id that allows me to send the reply to the requesting service. I'm not sure where to start with this. I'm thinking I will have 2 binding components (one for sending requests and another for handling replies). What I'm not sure about is what i need to do to make sure that the reply gets to the client instance that sent the original request. Ultimately here is what i would like to see happen: Client creates an InOut exchange and sync sends it to NMR. BC 1: formats and sends the request to a 3rd party system BC 2: recives the reply from 3rd party BC 2: formats a message (InOut/In/?) and sends it to NMR Client recieves the reply. I've looked through the samples and didn't see anything like this. Any help is greatly appreciated. Thanks -- View this message in context: http://www.nabble.com/Choreography-Orchestration-Question-tf3164899s12049.html#a8779749 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
