[ http://issues.apache.org/jira/browse/AXIS2-372?page=comments#action_12372610 ]
Thilina Gunarathne commented on AXIS2-372: ------------------------------------------ We can use two approches for this.. One approach is to provide the needed getStreams and other neccessary methodes to the MIMEHelper... Other solution is to introduce SOAPMessage and make it a place holder for attachments with neccessary attachment handling API.. IIRC there were loads of debates went on regarding the introduction of SOAPMessage. I can't remember whether we came to a conclusion... > Client API support Attachments (like Axis 1.X) > ---------------------------------------------- > > Key: AXIS2-372 > URL: http://issues.apache.org/jira/browse/AXIS2-372 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Priority: Blocker > > Use case: want to write an intermediary that peeks just the soap > headers and forwards messages with MTOM or SwA attachments. i don't > think our users can implement this with current public API. They would > have to muck around with the internals which can change. Also, we need > streaming support similar to one that was added in Axis 1.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
