I could be wrong but it looks like this is related to an issue I raised last
week where the JMSReplyTo header was not being preserved by Camel routing.
A fix went in, but it only added support for a few specific headers. So,
custom headers such as yours and also (I found today) things like AMQ's
JMSXGroupID are still not preserved by the routing.
I'm not sure if it's clear what the right answer is - should all headers get
propagated through the routing, or are some intended to "fall off"?
-Dominic
Nick Outram wrote:
>
> Settup:
>
> from("seda:in").beanRef("myBean").to("seda:out);
>
> with "myBean" defined in the spring application context as a pojo
> implementing the meathod read(String) and sending a message:
>
> template.send("seda:in", new Processor() {
> public void process(Exchange e) {
> Message in = exchange.getIn();
> in.setBody("Wibble");
> in.setHeader(BeanProcessor.METHOD_NAME, "read");
> }
> });
>
> doesn't result in a call to the read() method of the bean.
>
--
View this message in context:
http://www.nabble.com/MethodName-in-header-is-ignored-by-beanRef%28%29-tf4285009s22882.html#a12198390
Sent from the Camel - Users mailing list archive at Nabble.com.
