HI Fullocto, thanks very much for your valuable inputs.
Does this holds true even if we have a jms provider and jms consumer between JSR181(A) endpoint and JSR181(B) endpoint. You mentioned that component consumer will wait for for the response. Suppose user sends a message to JSR181(A) endpoint, which in turns routes it to JMS queue through JMS provider and then if i'm reitreving a message from the same jms queue through jms consumer and routing it to JSR181 (B) endpoint, how will i be able to send response from JSR181(b) endpoint back to JSR181(A) endpoint. best regards, tarandeep Fullocto wrote: > > 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-tp17292969p17316668.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
