On Tue, Mar 10, 2009 at 2:45 PM, orton <o_hu...@yahoo.com> wrote: > > > ≥Oh if you do NOT use the transferExchange=true option. eg if you send > ≥regular payload with Camel 1.6.0. > > ≥But yet again would be nice if you try the comitted fix. > > Hi Claus, am updating my Camel 2.0 code from repository and compiling now. > > Can you explain the transferExchange comment some more? Sorry, still a > little new to Camel and not sure how that option affects things? It marshal the entire Exchange, eg the container object in Camel used when routing messages. Its an option to use MINA as a kind of bridge between camel instances. So you can keep headers, properties etc. when you send the Exchange using Mina. Normally you only send the payload itself, eg the Body.
So when the Exchange is assembled on the other side it could contain stuff mina there could get confused over. But I really doubt it. I put my rely on the fix. But could you test with transferExchange=true and again with it =false > > Thanks again!! > > -- > View this message in context: > http://www.nabble.com/Camel-1.6-2.0-MINA-UDP-issue-tp22426433p22434468.html > Sent from the Camel - Development (activemq) mailing list archive at > Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
