Hi Viktoras,
I just checked to code of camel-service which implements the nmr component.
As the nmr component doesn't have the concept of protocol header which will be
put into the camel message header by default.
That could explain why you don't see the header when you use the
You should be able to find the header by reference the cxf message from camel
message like this
Message cxfMessage = camelMessage.getHeader("CamelCxfMessage");
String value = cxfMessage.get("XXX");
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
On Tuesday, November 6, 2012 at 2:10 PM, Viktoras wrote:
> Hi Willem,
>
> Thanks for reply; the header is named XXX and doesn't end in CXF.
>
> The weird part is that the header is filtered when CXF component address is
> NMR (actually ALL headers disappear in this case). If the address is changed
> to HTTP, everything works as expected. Can you please check the code snippet
> again?
>
> Thanks,
> Viktoras
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Headers-get-lost-Jetty-NMR-CXF-tp5722158p5722191.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
