eRouteBuilder() throws Exception {
>>>> return new RouteBuilder() {
>>>>
>>>> public void configure() throws Exception {
>>>> from("activemq:queue:hello")
>>>> .inOut()
public void process(Exchange exchange) throws
>>> Exception {
>>> exchange.getIn().setHeader("JMSReplyTo",
>>> "nameReplyQueue");
>>> exchange.getOut().setBody("What'
meReplyQueue"); //this should be enough
>> }
>> })
>> .setHeader("JMSReplyTo",constant("nameReplyQueue"))
>> // maybe this ?
>>
>> .setProperty("JMSReplyTo",
ot;)) // or this ?
>
> .to("activemq:queue:nameRequestor?preserveMessageQos=true");
> //this will force JMSReplyTo but won't correlate
> later.
>
> //.to("activemq:queue:nameRequestor?replyTo=queue:nameReplyQueue");
>
>
};
}
protected CamelContext createCamelContext() throws Exception {
CamelContext camelContext = super.createCamelContext();
amq = activeMQComponent(MQURI);
camelContext.addComponent("activemq", amq);
return camelContext;
}
}
--
View this message in context:
http://www.nabble.com/Still-problems-with-InOut-JMS-tp24363764p24363764.html
Sent from the Camel - Users mailing list archive at Nabble.com.
