Ah - no I didn't - that's much neater. Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/SJMS-component-and-IBM-Websphere-MQ-quirks-tp5740588p5740699.html
Sent from the Camel - Users mailing list archive at Nabble.com.
; exchange.getIn().removeHeader("JMS_IBM_MsgType");
>}
>})
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/SJMS-component-and-IBM-Websphere-MQ-quirks-tp5740588p5740596.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
@Override
> public void process(Exchange exchange) throws
> Exception {
>
> exchange.getIn().removeHeader("JMS_IBM_MsgType");
> }
> })
>
>
>
> --
> View this message in context:
&g
rride
public void process(Exchange exchange) throws
Exception {
exchange.getIn().removeHeader("JMS_IBM_MsgType");
}
})
--
View this message in context:
http://camel.465427.n5.nabble.com/SJMS-co
s over the jms - had weird infinite loops when an
app sends a message to one of its own queues wanting a reply - I suspect
this is due to the reply destination copying!!!
--
View this message in context:
http://camel.465427.n5.nabble.com/SJMS-component-and-IBM-Websphere-MQ-quirks-tp5740588.html
