Unfortunately I am still not able to get this working. What do I want to do with it:
1. a user uploads a file using a simple upload form 2. when hitting the send button, the form data is send to the http-consumer 3. the http consumer uses InOut MEP and is forwarding the message to the handler bean 4. the handler bean is extracting the data (name and content of the file) 5. the handler is modifying the file contents (for example converting to another file format) 6. the handler fills the modified file to the attachment of the out message 7. the handler fills the content of the out message with <payload/> as dummy content 8. the handler sends the message back to the http-consumer 9. the browser now pops up a window to save the modified file thats it... The reality is a little different. Up to point 8 everything works fine. Step 9 is not working. The browser gets some multipart message but not containing any file content. (see the posts in this thread) I would expect that if I send a out message to the http-consumer, only containing an attachment and a dummy xml content (maybe here an empty content should be made allowed) that this attachment is used to put out a stream to the client, sending the pure file. (as a download would work) The question is now if my expectations are that wrong or is smix just not working as it should? What I try to prevent is making my own jetty binding component for that issue. Thanks for any advice, Lars -- View this message in context: http://www.nabble.com/Help-with-http-upload-component-tf4810196s12049.html#a13873100 Sent from the ServiceMix - User mailing list archive at Nabble.com.
