Camel stores information in various headers and information related to original queue can be captured from the same. Based on the scenario/use case this information can be used dynamically as well to route the message [ Routing slip EIP ]. Is this what you are looking for ? It will be great if you can explain your use case with respect to camel in detail.
On Tue, Jun 2, 2015 at 3:41 PM, mohanradhakrishnan < [email protected]> wrote: > I am new to EIP. Recently I came across code that serializes > com.ibm.mq.jms.MQQueue. This is done in order to remember which queue to > post to when the downstream queues - there are multiple layers of queues - > respond later. > > Can someone help me understand how an integration framework caches or > figures out which queue originated the message ? This message is passed on > to another queue and so on. Later we receive the response and post it back > to the originating queue. > > What EIP pattern covers this ? Any Camel sample ? > > Thanks, > Mohan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Caching-the-upstream-queue-tp5767790.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- - Ravi *[ View My Youtube Channel <https://www.youtube.com/playlist?list=PL5Y_TlNjh0D59A4K3yQQR7gNAslnxDmRB> ]* Phone: +91 *98 509 760 91*
