FYI, the MTOM support only affects servicemix-jsr181, not the servicemix-http component. MTOM will only help to reference the attachment from the xml content.
In all cases, the best way to deal with binary contents is to use attachments. It will avoid unnecessary marshalling. servicemix-http support attachments by using MIME HTTP requests instead of a simple POST request, but there is no support for binary HTTP requests / responses. On 8/4/06, apinke <[EMAIL PROTECTED]> wrote:
Hi Guillaume , Is this change in the last snapshot ? or do I have to build from the sources ? Also , Is there a example that shows how I can do this ? I have a situation where a HTTP response from an external system will return a tiff/pdf . ... the servlet reponse gets converted into a byte[] . Is there a efficient way to pass this byte[] around through all the ESB components and finally out through a HTTP BC ? I see 3 options but ont sure which is most effective : 1) convert the byte[] into base64 encoded string and set that in an dummy xml and pass that in the context.. 2) use xtream to serialize the Object that contains the byte[] 3) Store the byte[] as binary attachement .. Is there any better way for doing this and avoid the encoding or marshalling ? I am not exactly sure how MTOM can be used thanks Pat -- View this message in context: http://www.nabble.com/MTOM-support-in-servicemix-jsr181-tf2042101.html#a5650046 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
