You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Tony Dean <To...@sas.com> on 2008/06/03 22:40:57 UTC
[Axis2] response content
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 (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5
X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
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 (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5
X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
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:93D2E13819F92A45691212524849949@apache.org"; 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....@apache.org>
<?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
tony.dean@sas.com
SAS... The Power to Know
http://www.sas.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] response content
Posted by Thilina Gunarathne <cs...@gmail.com>.
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 <To...@sas.com> 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:93D2E13819F92A45691212524849949@apache.org<0....@apache.org>";
> 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....@apache.org>
> >
>
> <?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
> tony.dean@sas.com
>
> SAS... The Power to Know
> http://www.sas.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
Re: [Axis2] response content
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
I have a Flash/Flex consumer that is not working properly because it
> cannot handle multipart/related content type. It is treating the post
> response, mime boundary and all, as the soap envelope.
>
>
>
> It seems that enableMTOM=optional is not fail proof since a client can be
> optimized not to send MTOM if there are no outgoing attachements.
>
Yeah... I know it's not ideal, but I think above is a good compromise for
both the scenerio's..
Ideal way would be to use MTOM policy if somebody needs this much of
precision...
> I guess my best solution is to enable MTOM at the service operation
> level only when I know that a particular operation will return an
> attachment.
>
> I assume you do this as follows:
>
> <service name=""?
>
> <description>…</description>
>
> <operation name="…">
>
> <messageReceiver class="…"/>
>
> <parameter name="enableMTOM">true</parameter>
>
> </operation>
>
> …
>
> </service>
>
Above is the correct way to enable/disable MTOM per operation wise.
> This way I will return MTOM only if attachments are in the response;
> otherwise, contentType=text/xml will be returned when no attachments are
> present. Does this sound right?
>
Nope... MIME envelope will be there in the respose message irrespective of
whether there is an attachment or not :(..
thanks,
Thilina
>
>
> Thanks.
>
>
>
>
>
> *From:* Thilina Gunarathne [mailto:csethil@gmail.com]
> *Sent:* Thursday, June 05, 2008 2:58 AM
> *To:* axis-user@ws.apache.org
> *Cc:* axis-dev@ws.apache.org
> *Subject:* Re: [Axis2] response content
>
>
>
> Is it whether my following reply did not answer ur questions or whether you
> simply missed it..
> http://markmail.org/message/lt65mrgnkr7egqjk
>
> The earlier mails in axis-dev related to this...
> http://markmail.org/message/rrtsu7x22pkwya2e
>
> IMHO I do not think this as a much of a limitation given that users can
> enable MTOM per operation wise and also they can use "optional" for
> enableMTOM..
>
> thanks,
> Thilina
>
> On Wed, Jun 4, 2008 at 10:28 PM, Tony Dean <To...@sas.com> wrote:
>
> Anyone have any answers to the question below. Thanks.
>
>
> > -----Original Message-----
> > From: Tony Dean [mailto:Tony.Dean@sas.com]
> > Sent: Tuesday, June 03, 2008 4:41 PM
> > To: axis-dev@ws.apache.org
> > Subject: [Axis2] response content
> >
> > 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:93D2E13819F92A45691212524849949@apache.org<0....@apache.org>";
> 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....@apache.org>
> >
> >
> > <?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
> > tony.dean@sas.com
> >
> > SAS... The Power to Know
> > http://www.sas.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
Re: [Axis2] response content
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
I have a Flash/Flex consumer that is not working properly because it
> cannot handle multipart/related content type. It is treating the post
> response, mime boundary and all, as the soap envelope.
>
>
>
> It seems that enableMTOM=optional is not fail proof since a client can be
> optimized not to send MTOM if there are no outgoing attachements.
>
Yeah... I know it's not ideal, but I think above is a good compromise for
both the scenerio's..
Ideal way would be to use MTOM policy if somebody needs this much of
precision...
> I guess my best solution is to enable MTOM at the service operation
> level only when I know that a particular operation will return an
> attachment.
>
> I assume you do this as follows:
>
> <service name=""?
>
> <description>…</description>
>
> <operation name="…">
>
> <messageReceiver class="…"/>
>
> <parameter name="enableMTOM">true</parameter>
>
> </operation>
>
> …
>
> </service>
>
Above is the correct way to enable/disable MTOM per operation wise.
> This way I will return MTOM only if attachments are in the response;
> otherwise, contentType=text/xml will be returned when no attachments are
> present. Does this sound right?
>
Nope... MIME envelope will be there in the respose message irrespective of
whether there is an attachment or not :(..
thanks,
Thilina
>
>
> Thanks.
>
>
>
>
>
> *From:* Thilina Gunarathne [mailto:csethil@gmail.com]
> *Sent:* Thursday, June 05, 2008 2:58 AM
> *To:* axis-user@ws.apache.org
> *Cc:* axis-dev@ws.apache.org
> *Subject:* Re: [Axis2] response content
>
>
>
> Is it whether my following reply did not answer ur questions or whether you
> simply missed it..
> http://markmail.org/message/lt65mrgnkr7egqjk
>
> The earlier mails in axis-dev related to this...
> http://markmail.org/message/rrtsu7x22pkwya2e
>
> IMHO I do not think this as a much of a limitation given that users can
> enable MTOM per operation wise and also they can use "optional" for
> enableMTOM..
>
> thanks,
> Thilina
>
> On Wed, Jun 4, 2008 at 10:28 PM, Tony Dean <To...@sas.com> wrote:
>
> Anyone have any answers to the question below. Thanks.
>
>
> > -----Original Message-----
> > From: Tony Dean [mailto:Tony.Dean@sas.com]
> > Sent: Tuesday, June 03, 2008 4:41 PM
> > To: axis-dev@ws.apache.org
> > Subject: [Axis2] response content
> >
> > 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:93D2E13819F92A45691212524849949@apache.org<0....@apache.org>";
> 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....@apache.org>
> >
> >
> > <?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
> > tony.dean@sas.com
> >
> > SAS... The Power to Know
> > http://www.sas.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
RE: [Axis2] response content
Posted by Tony Dean <To...@sas.com>.
Thilina,
Sorry I must have missed it. Also, I had forgotten some of the specifics about why an MTOM message is generated even though there are no attachments in the response due to optimization reasons.
I have a Flash/Flex consumer that is not working properly because it cannot handle multipart/related content type. It is treating the post response, mime boundary and all, as the soap envelope.
It seems that enableMTOM=optional is not fail proof since a client can be optimized not to send MTOM if there are no outgoing attachements.
I guess my best solution is to enable MTOM at the service operation level only when I know that a particular operation will return an attachment.
I assume you do this as follows:
<service name=""?
<description>...</description>
<operation name="...">
<messageReceiver class="..."/>
<parameter name="enableMTOM">true</parameter>
</operation>
...
</service>
This way I will return MTOM only if attachments are in the response; otherwise, contentType=text/xml will be returned when no attachments are present. Does this sound right?
Thanks.
From: Thilina Gunarathne [mailto:csethil@gmail.com]
Sent: Thursday, June 05, 2008 2:58 AM
To: axis-user@ws.apache.org
Cc: axis-dev@ws.apache.org
Subject: Re: [Axis2] response content
Is it whether my following reply did not answer ur questions or whether you simply missed it..
http://markmail.org/message/lt65mrgnkr7egqjk
The earlier mails in axis-dev related to this...
http://markmail.org/message/rrtsu7x22pkwya2e
IMHO I do not think this as a much of a limitation given that users can enable MTOM per operation wise and also they can use "optional" for enableMTOM..
thanks,
Thilina
On Wed, Jun 4, 2008 at 10:28 PM, Tony Dean <To...@sas.com>> wrote:
Anyone have any answers to the question below. Thanks.
> -----Original Message-----
> From: Tony Dean [mailto:Tony.Dean@sas.com<ma...@sas.com>]
> Sent: Tuesday, June 03, 2008 4:41 PM
> To: axis-dev@ws.apache.org<ma...@ws.apache.org>
> Subject: [Axis2] response content
>
> 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:80>
> Date: Tue, 03 Jun 2008 20:10:23 GMT
> X-Cache: MISS from inetgw04.unx.sas.com<http://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:80>
> Date: Tue, 03 Jun 2008 20:27:29 GMT
> X-Cache: MISS from inetgw04.unx.sas.com<http://inetgw04.unx.sas.com>
> Content-Type: multipart/related;
> boundary=MIMEBoundaryurn_uuid_93D2E13819F92A45691212524849948;
> type="application/xop+xml";
> start="0.urn:uuid:93D2E13819F92A45691212524849949@apache.org<ma...@apache.org>"; 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....@apache.org>>
>
> <?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
> tony.dean@sas.com<ma...@sas.com>
>
> SAS... The Power to Know
> http://www.sas.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org<ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org<ma...@ws.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org<ma...@ws.apache.org>
For additional commands, e-mail: axis-user-help@ws.apache.org<ma...@ws.apache.org>
--
Thilina Gunarathne - http://thilinag.blogspot.com
RE: [Axis2] response content
Posted by Tony Dean <To...@sas.com>.
Thilina,
Sorry I must have missed it. Also, I had forgotten some of the specifics about why an MTOM message is generated even though there are no attachments in the response due to optimization reasons.
I have a Flash/Flex consumer that is not working properly because it cannot handle multipart/related content type. It is treating the post response, mime boundary and all, as the soap envelope.
It seems that enableMTOM=optional is not fail proof since a client can be optimized not to send MTOM if there are no outgoing attachements.
I guess my best solution is to enable MTOM at the service operation level only when I know that a particular operation will return an attachment.
I assume you do this as follows:
<service name=""?
<description>...</description>
<operation name="...">
<messageReceiver class="..."/>
<parameter name="enableMTOM">true</parameter>
</operation>
...
</service>
This way I will return MTOM only if attachments are in the response; otherwise, contentType=text/xml will be returned when no attachments are present. Does this sound right?
Thanks.
From: Thilina Gunarathne [mailto:csethil@gmail.com]
Sent: Thursday, June 05, 2008 2:58 AM
To: axis-user@ws.apache.org
Cc: axis-dev@ws.apache.org
Subject: Re: [Axis2] response content
Is it whether my following reply did not answer ur questions or whether you simply missed it..
http://markmail.org/message/lt65mrgnkr7egqjk
The earlier mails in axis-dev related to this...
http://markmail.org/message/rrtsu7x22pkwya2e
IMHO I do not think this as a much of a limitation given that users can enable MTOM per operation wise and also they can use "optional" for enableMTOM..
thanks,
Thilina
On Wed, Jun 4, 2008 at 10:28 PM, Tony Dean <To...@sas.com>> wrote:
Anyone have any answers to the question below. Thanks.
> -----Original Message-----
> From: Tony Dean [mailto:Tony.Dean@sas.com<ma...@sas.com>]
> Sent: Tuesday, June 03, 2008 4:41 PM
> To: axis-dev@ws.apache.org<ma...@ws.apache.org>
> Subject: [Axis2] response content
>
> 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:80>
> Date: Tue, 03 Jun 2008 20:10:23 GMT
> X-Cache: MISS from inetgw04.unx.sas.com<http://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:80>
> Date: Tue, 03 Jun 2008 20:27:29 GMT
> X-Cache: MISS from inetgw04.unx.sas.com<http://inetgw04.unx.sas.com>
> Content-Type: multipart/related;
> boundary=MIMEBoundaryurn_uuid_93D2E13819F92A45691212524849948;
> type="application/xop+xml";
> start="0.urn:uuid:93D2E13819F92A45691212524849949@apache.org<ma...@apache.org>"; 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....@apache.org>>
>
> <?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
> tony.dean@sas.com<ma...@sas.com>
>
> SAS... The Power to Know
> http://www.sas.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org<ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org<ma...@ws.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org<ma...@ws.apache.org>
For additional commands, e-mail: axis-user-help@ws.apache.org<ma...@ws.apache.org>
--
Thilina Gunarathne - http://thilinag.blogspot.com
Re: [Axis2] response content
Posted by Thilina Gunarathne <cs...@gmail.com>.
Is it whether my following reply did not answer ur questions or whether you
simply missed it..
http://markmail.org/message/lt65mrgnkr7egqjk
The earlier mails in axis-dev related to this...
http://markmail.org/message/rrtsu7x22pkwya2e
IMHO I do not think this as a much of a limitation given that users can
enable MTOM per operation wise and also they can use "optional" for
enableMTOM..
thanks,
Thilina
On Wed, Jun 4, 2008 at 10:28 PM, Tony Dean <To...@sas.com> wrote:
> Anyone have any answers to the question below. Thanks.
>
> > -----Original Message-----
> > From: Tony Dean [mailto:Tony.Dean@sas.com]
> > Sent: Tuesday, June 03, 2008 4:41 PM
> > To: axis-dev@ws.apache.org
> > Subject: [Axis2] response content
> >
> > 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 (build: SVNTag=JBoss_4_2_1_GA
> > date=200707131605)/Tomcat-5.5
> > X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> > 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 (build: SVNTag=JBoss_4_2_1_GA
> > date=200707131605)/Tomcat-5.5
> > X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> > 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:93D2E13819F92A45691212524849949@apache.org<0....@apache.org>";
> 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....@apache.org>
> >
> >
> > <?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
> > tony.dean@sas.com
> >
> > SAS... The Power to Know
> > http://www.sas.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
Re: [Axis2] response content
Posted by Thilina Gunarathne <cs...@gmail.com>.
Is it whether my following reply did not answer ur questions or whether you
simply missed it..
http://markmail.org/message/lt65mrgnkr7egqjk
The earlier mails in axis-dev related to this...
http://markmail.org/message/rrtsu7x22pkwya2e
IMHO I do not think this as a much of a limitation given that users can
enable MTOM per operation wise and also they can use "optional" for
enableMTOM..
thanks,
Thilina
On Wed, Jun 4, 2008 at 10:28 PM, Tony Dean <To...@sas.com> wrote:
> Anyone have any answers to the question below. Thanks.
>
> > -----Original Message-----
> > From: Tony Dean [mailto:Tony.Dean@sas.com]
> > Sent: Tuesday, June 03, 2008 4:41 PM
> > To: axis-dev@ws.apache.org
> > Subject: [Axis2] response content
> >
> > 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 (build: SVNTag=JBoss_4_2_1_GA
> > date=200707131605)/Tomcat-5.5
> > X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> > 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 (build: SVNTag=JBoss_4_2_1_GA
> > date=200707131605)/Tomcat-5.5
> > X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> > 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:93D2E13819F92A45691212524849949@apache.org<0....@apache.org>";
> 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....@apache.org>
> >
> >
> > <?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
> > tony.dean@sas.com
> >
> > SAS... The Power to Know
> > http://www.sas.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://thilinag.blogspot.com
RE: [Axis2] response content
Posted by Tony Dean <To...@sas.com>.
Anyone have any answers to the question below. Thanks.
> -----Original Message-----
> From: Tony Dean [mailto:Tony.Dean@sas.com]
> Sent: Tuesday, June 03, 2008 4:41 PM
> To: axis-dev@ws.apache.org
> Subject: [Axis2] response content
>
> 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 (build: SVNTag=JBoss_4_2_1_GA
> date=200707131605)/Tomcat-5.5
> X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> 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 (build: SVNTag=JBoss_4_2_1_GA
> date=200707131605)/Tomcat-5.5
> X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> 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:93D2E13819F92A45691212524849949@apache.org"; 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....@apache.org>
>
> <?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
> tony.dean@sas.com
>
> SAS... The Power to Know
> http://www.sas.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [Axis2] response content
Posted by Tony Dean <To...@sas.com>.
Anyone have any answers to the question below. Thanks.
> -----Original Message-----
> From: Tony Dean [mailto:Tony.Dean@sas.com]
> Sent: Tuesday, June 03, 2008 4:41 PM
> To: axis-dev@ws.apache.org
> Subject: [Axis2] response content
>
> 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 (build: SVNTag=JBoss_4_2_1_GA
> date=200707131605)/Tomcat-5.5
> X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> 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 (build: SVNTag=JBoss_4_2_1_GA
> date=200707131605)/Tomcat-5.5
> X-Cache-Lookup: MISS from inetgw04.unx.sas.com:80
> 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:93D2E13819F92A45691212524849949@apache.org"; 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....@apache.org>
>
> <?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
> tony.dean@sas.com
>
> SAS... The Power to Know
> http://www.sas.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org