Gerorge Have you tried to use your own codec? There is a codec parameter to the uri configuration of camel routes.
The codec is then your Mina codec class where you can do the encode/decode where you can include the headers and properties from the exchange. I am however not sure if using this codec it gives you access to the exchange in your subclass? Another approach is to do your own data format, there is some examples in Camel where you can create your data formatter and annotate them. Then you can have your dataforma POJO class that holds the body, header and properties. You are ofcourse welcome to try to create a patch for camel that includes the header and properties out-of-the-box. It is however not so easy as the raw TCP protocol is not a protocol that supports metadata as headers and properties = everything is one long binary stream. Unlike eg. messaging such as JMS. /Claus georgiosgeorgiadis wrote: > > Hi Claus, > > Yes, the requirement is that we connect to a local or TCP repository with > the ability to switch from the one or the other only with configuration > changes. The thing is that we specify some of the stuff in the headers and > the properties and they don't seem to be passed when I use mina tcp camel > endpoint. > > Regards > > Georgios > > > davsclaus wrote: >> >> Hi George >> >> camel-mina does only support marshalling the body content. (in.body) >> What is you use-case for using camel-mina to send messages that contains >> headers and properties as well? >> >> /Claus >> > > -- View this message in context: http://www.nabble.com/Camel-TCP-receiver-endpoint-tp15430834s22882p15950769.html Sent from the Camel - Users mailing list archive at Nabble.com.
