Hi
Instead of using the customer processor, the route can use the convertBodyTo
directly.
Willem
--
View this message in context:
http://camel.465427.n5.nabble.com/Cometd-component-tp4299174p4300424.html
Sent from the Camel - Users mailing list archive at
Thanks for the suggestion.
I have found the conceptual problem on my side; the XStream / Jackson
marshalling both created a Byte array as the body of the message based on
the Object, not a string formatted as "{[name]:[value]}". I thus expected to
receive something like
"{value:123,name:"Foo",..
Have you tried using the Jackson library instead of Xstream?
There is Jackson support in camel greater than 2.0
(http://camel.apache.org/json.html). I haven't used the Camel Jackson
component but if it works anything like the regular jackson libraries it
should be straight forward with no annotati
