Hi, I think we had the same conversation years back. Originally Axis2 MTOMised the message only if there were optimised attachements in the message. But this had the drawback of needing to traverse the whole message building the OM tree looking for opitmisable attachments. On the other hand there were interoperability issues with WCF as it expects the MIME boundary when MTOM is enabled regardless whether there are attachments or not. Then only we decided to fall back to this model. I'm sure you can find many discussions regarding this in the Axis2 mail archives. Ideally it's the MTOM policy that should control this behaviour.
Also you can use "optional" as the value for enableMTOM parameter as mentioned below. http://thilinag.blogspot.com/2007/07/improved-apache-axis2-attachment.html thanks, Thilina On Tue, Jun 3, 2008 at 1:40 PM, Tony Dean <[EMAIL PROTECTED]> wrote: > Hi, > > I have a web service that is returning XML... it's schema type is xsd:any. > I would expect the content to be returned as follows: > > HTTP/1.0 200 OK > Content-Type: text/xml > > <?xml version='1.0' encoding='UTF-8'?> > <soapenv:Envelope> > <soapenv:Body> > ... > </soapenv:Body> > </soapenv:Envelope> > > > I would expect this to be returned whether MTOM is enabled or not. > Wouldn't you? > > > Here's the response from Axis2 service when MTOM is disabled in the > Axis2.conf server config file: > > HTTP/1.0 200 OK > Proxy-Connection: close > X-Powered-By: Servlet 2.4; JBoss-4.2.1.GA <http://jboss-4.2.1.ga/> (build: > SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5 > X-Cache-Lookup: MISS from > inetgw04.unx.sas.com:80<http://inetgw04.unx.sas.com/> > Date: Tue, 03 Jun 2008 20:10:23 GMT > X-Cache: MISS from inetgw04.unx.sas.com > Content-Type: text/xml;charset=UTF-8 > Server: Apache-Coyote/1.1 > > <?xml version='1.0' encoding='UTF-8'?> > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ > "> > <soapenv:Body> > ..... > </soapenv:Body> > </soapenv:Envelope> > > > Looks correct. > > > ------------------------------------------------------------------------------------------------------------------------ > > Here's the response from Axis2 service when MTOM is enabled in the > Axis2.conf server config file: > > HTTP/1.0 200 OK > Proxy-Connection: close > X-Powered-By: Servlet 2.4; JBoss-4.2.1.GA <http://jboss-4.2.1.ga/> (build: > SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5 > X-Cache-Lookup: MISS from > inetgw04.unx.sas.com:80<http://inetgw04.unx.sas.com/> > Date: Tue, 03 Jun 2008 20:27:29 GMT > X-Cache: MISS from inetgw04.unx.sas.com > Content-Type: multipart/related; > boundary=MIMEBoundaryurn_uuid_93D2E13819F92A45691212524849948; > type="application/xop+xml"; start=" > 0.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]>"; > start-info="text/xml" > Server: Apache-Coyote/1.1 > > --MIMEBoundaryurn_uuid_93D2E13819F92A45691212524849948 > Content-Type: application/xop+xml; charset=UTF-8; type="text/xml" > Content-Transfer-Encoding: binary > Content-ID: <0.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]> > > > > <?xml version='1.0' encoding='UTF-8'?> > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ > "> > <soapenv:Body> > .... > </soapenv:Body> > </soapenv:Envelope> > > > Why use multipart/related content type when there are no attachments? That > is, why make an attachment out of the SOAP envelope itself when there are > no real attachments? Is this correct behavior? > > I'd like to hear your comments. > > 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] > > -- Thilina Gunarathne - http://thilinag.blogspot.com
