Hi, Nope... You can't control it.. Initial MOTM impl on Axis2 was designed to support your case by default. But with that model we ran in to performance issues as well as interoperability issues with other SOAP stacks. With that behaviour we had to walk through the whole SOAP message to see whether there are any optimised OMText objects present, which eventually causes the tree to be built.
Sometime back(just prior to 1.0) after loads of discussions(can't remember whether at the mailing list or at the Axis2 weekly chat we used to have), we took a decision to change it to the current behaviour. Ideally enabling MTOM should happen at the policy level. But unfortunately MTOM policy specs are yet to come. Regards, ~Thilina On 9/19/06, Tony Dean <[EMAIL PROTECTED]> wrote:
Hi, I have a question regarding MTOM attachments. I'm running with MTOMEnabled=true... Sometimes however, when I do not have an attachment (OMText(dataHandler, true) to return to the client, I would like to send the soap:Envelope response w/o using MIME attachments. But even in this case, my response is sent as a single attachment containing just the soap:Envelope since there are no real attachments. Is there a way to control this behavior such that in this case the response is not embedded in a MIME part. Thanks. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] SAS... The Power to Know http://www.sas.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
