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-tp15430834s22882p15950664.html Sent from the Camel - Users mailing list archive at Nabble.com.
