Hi, It's not in the way you create the message. It is how the message looks like in the wire.. MTOM can be considered as a special case of SwA.. Even though MTOM includes <xop:include> tags, it is possible to extract the attachment using SwA enabled web service processor.
See here[1] too.. thanks, Thilina [1]http://ws.apache.org/axis2/1_3/mtom-guide.html#33 On Feb 19, 2008 3:18 AM, <[EMAIL PROTECTED]> wrote: > > Hi, > > Is it possible to create an endpoint operation that can respond either MTOM > or SwA depending on the request? > > I read the Attachments/MTOM guide and first I understood it as MTOM was > already backward compatible with SwA. > But if I enable MTOM for my endpoint it always returns a xop:include (mtom) > no matter how i call the service. > And if I enable SwA instead of MTOM for the endpoint it still returns a > xop:include but with an empty attachment. > > Afterwards I read the following article "http://wso2.org/library/1675"; and > I could then see the implementation for > SwA was different from MTOM. You manually add your attachment to the > outgoing MessageContext where as MTOM > uses OMText on OMFactory. > > Can I conclude that it isn't possible to create an MTOM endpoint operation > that is backward compatible with SwA? > > Regards > Multi-Support A/S > > Torben Riis > -------------------------------------------------------------------- > Phone +45 96 600 600, Fax +45 96 600 601 > E-mail: [EMAIL PROTECTED] > http://www.multi-support.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thilina Gunarathne - http://thilinag.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
