On 1/9/07 12:56 PM, "MrRothstein" <[EMAIL PROTECTED]> wrote: > > Daryl Richter-3 wrote: >> >> Ah, ok. But since you want your process to be synchronous anyway, why do >> you need Component 3? If Component 2 formats both directions your problem >> is solved. >> > > I would like the "integeration components ( 2 and 3) " to be capable of high > through puts. These components should be available for a large number of > clients (component 1) types. My thinking is that it is better to tie up > threads at the client level vs. the shared component.
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. :) > > In general it sounds like only those components that have direct access to > the JMSReplyTo destination are able to send messages to it. Is that > correct? Yes and no. It is meant to be a "special" destination and how it is handled when sending in a request/reply fashion is implementation and possibly context specific. You can, however, manipulate it directly if you want to. 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. -- Daryl http://itsallsemantics.com
