Re: MTOM message part not formatted correctly according to RFC 1341 using CRLFLF instead of CRLFCRLF

This bug is fixed in CXF-4482!+ -- View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737610.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: MTOM message part not formatted correctly according to RFC 1341 using CRLFLF instead of CRLFCRLF

Hi Claus, We are using: - Camel 2.9.2 - CXF 2.6.3 - Java 1.6 - Suse Linux From the logs, it looks like they are using the Apache Coyote 1.1 connector with their Tomcat server. Clay -- View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly

Re: MTOM message part not formatted correctly according to RFC 1341 using CRLFLF instead of CRLFCRLF

Is there a fix for this in Camel 2.11.1? -- View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737441.html Sent from the Camel - Users mailing list archive at Nabble.com.

MTOM message part not formatted correctly according to RFC 1341 using CRLFLF instead of CRLFCRLF

specification: - http://www.w3.org/Protocols/rfc1341/0_TableOfContents.html - http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html Is this a known issue in Apache Camel or is there another explanation? Thanks, Clay -- View this message in context: http://camel.465427.n5.nabble.com/MTOM

message.copy() Does not perform deep copy of the message body.

I am trying to copy a message so that I can alter it for subsequent processing Message newMessage = message.copy(); but the MessageSupport.copyFrom() method (which is called from MessageSupport.copy() ) does not copy the original message body to the newMessage body, but only a reference to