Daryl Richter-3 wrote: > > I'm not sure how splitting 2 and 3 helps you here if you are assuming > synchronous calls because you are still limited by the throughput of the > external system, but see below. :) > I might not be thinking about this correctly. I'm picturing client applications (component 1) blocking and waiting for replies. However, components 2 and 3 will be shared resources and would be able to send and recieve messages without blocking for many clients.
Being able to recreate the temp destination and send the replies to it would also simplify correlation logic. Daryl Richter-3 wrote: > > Typing that made me think... Is your external system preserving the > ReplyTo > of the inbound message on the outbound message? (Essentially ignoring it) > > If yes, then you can do what you want. Component 2 just copies the > incoming > ReplyTo (Component 1's address) into its outgoing ReplyTo, Component 3 > takes > the incoming ReplyTo (still Component 1's address) sends its result to it. > This is basically what I'm looking to do. However, the external system is not based on JMS. I can't get a Destination object to come back from it on the reply. I was hoping to be able to recreate a reference to the destination from a string. Doesn't look like this is supported by the spec though. Going to look at servicemix and see if it supports what I'm looking to do. Thanks for the taking the time to reply. -- View this message in context: http://www.nabble.com/Working-with-temporary-queues-tf2944057.html#a8250911 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
