Thanks Tarun, for your opinion. Don't think about the
.wireTap(recorder)
in this context... it's just used to dump all the messages going thru this
route. In my 'real' code it's even configurable how this recorder shall
work: into a file, into a queue, or into
"direct:dustbin"
which will be emptied with
from("direct:dustbin").stop();
Back to my issue. So, I cannot fully decouple the endpoint definitions (by
putting them into Spring XML) from the message routing (implemented in JAVA
DSL): whenever - now or later - it is decided to inject a WMQ queue as
destination (which is by now e.g. an Oracle queue or a file), I had to
change the JAVA code by adding a
.removeHeaders("JMS*")
Or, to be prepared for all eventualities, I will add this .removeHeader()
statement in front of all .to() statements of all routes! But if I'm forced
to do so, I wonder if this should not be the task for Camel - at least for
WMQ endpoints - to remove the JMS* headers, to be complied with WebSphere
and comfortable for the Camel user?
--
View this message in context:
http://camel.465427.n5.nabble.com/WebSphere-MQ-bridging-messages-from-Oracle-AQ-fails-with-com-ibm-msg-client-jms-DetailedMessageFormat-tp4390504p4392541.html
Sent from the Camel - Users mailing list archive at Nabble.com.
