If the message exchange pattern is an IN/OUT, each message exchange (ME) (kind of normalized messages container "linking" a component consumer and a component provider) will wait for the response.
You have two choices to create a chain, either you use camel or in your JSR181 components, you use servicemix client api (used to call a JBI service): I will speak about this last solution. During the send of the request, the message will follow this path: (light version) user -> BC Consumer [ME1] NMR [ME1-mirrored] JSR181 [ME2] NMR [ME2-mirrored] BC provider -> external service When you send the request, it will create different ME (1 and 2) that will wait for the response, so you don't have to focus on the routage of coming back messages. -- View this message in context: http://www.nabble.com/Message-exchange-tp17292969p17316658.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
