2010/5/19 Claus Ibsen <[email protected]>:
> On Wed, May 19, 2010 at 6:43 AM, Muhammad Ichsan <[email protected]> wrote:
>> 2010/5/18 Claus Ibsen <[email protected]>:
>>> Try without ?replyTo=out
>>
>
> Do something simpler and then add to the route.
> For example using only JMS, mock etc. to have a simple test starting.
>
> And InOut over JMS works transparent, so you do not have to send to
> the OUT queue or mess with correlation ids etc.
1. Don't mess with correlation id? Shouldn't we set the correlation id
in order to make the inOut ends?
2. Where can I read more to understand InOut pattern. I want to know,
when to use exchange.getOut() and when to use getIn()
This is my actual problem
1. I need to send an X type message into a server
2. The server only accept Y type message and it will respond in Y type
response message too.
This way, I create:
from("activemq:input").to("bean:converter?method=keepCorrelationIdAndTranslateToY").to("direct:serverInput");
from("direct:serverOutput").to("bean:converter?method=translateToXAndSetCorrelationId").to("activemq:out")
from("direct:process").to("activemq:input?replyTo=out").to("file://tmp/result.txt")
Thanks
--
~The best men are men who benefit to others
http://michsan.web.id 一緒に勉強しましょう！
Yang berkualitas memang beda rasanya!
http://rizqi-cookies.com
