You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Yong Yang <y....@querix.com> on 2007/10/11 17:23:19 UTC
the problem of enabling MTOM in web service client in AXIS2/C
Hi everyone,
I wrote a web service client test case using AXIS2/C 1.0 to access a simple web service. In the client, I have enabled MTOM even if there is no binaary attachment to send in fact. I got one exception(see [1] and [2]).
Then I compared the soap request created by AXIS2/C 1.0 with the soap request created by AXIS2 1.2. I found the major difference is that the value of start-info is "application/xop+xml" not "text/xml" in the soap request created by AXIS2/C. Is there any API to set the start-info? if not, how can I solve this issue? Many thanks in advance.
best regards
yong
[1] soap request created by axis2/c
POST /axis2/services/simple_int HTTP/1.1
User-Agent: Axis2/C
Content-Length: 555
Content-Type: multipart/related; boundary=MIMEBoundaryc4bffdc7-918b-40ee-bacf-9ce9962d479b; type="application/xop+xml"; start="< 0.10302e03-c3be-422f-b33b-a8a2a4880a6f@apache.org>"; start-info="application/soap+xml"; charset="UTF-8";action=""""
Host: 127.0.0.1:9000
--MIMEBoundaryc4bffdc7-918b-40ee-bacf-9ce9962d479b
content-transfer-encoding: binary
content-id: < 0.10302e03-c3be-422f-b33b-a8a2a4880a6f@apache.org>content-type: application/xop+xml; charset=UTF-8; type="application/soap+xml";
<soapenv:Envelope xmlns:soapenv=" http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header></soapenv:Header>
<soapenv:Body>
<ns1:int_input_outputMessage xmlns:ns1=" http://querix.com/xsd">
<param0>10</param0>
</ns1:int_input_outputMessage>
</soapenv:Body>
</soapenv:Envelope>--MIMEBoundaryc4bffdc7-918b-40ee-bacf-9ce9962d479b--
[2] soap reply for the soap request created by axis2/c
HTTP/1.1 400 Bad Request
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; action=" http://www.w3.org/2005/08/addressing/soap/fault";charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 11 Oct 2007 13:24:51 GMT
Connection: close
241
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope ">
<soapenv:Header>
<wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">Invalid Content Type Field in the Mime Message</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail></soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
[3] soap request created by AXIS2 java
POST /axis2/services/simple_int HTTP/1.1
SOAPAction: "urn:int_input_output"
User-Agent: Axis2
Host: 127.0.0.1:9000
Transfer-Encoding: chunked
Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841; type="application/xop+xml"; start="< 0.urn:uuid:0CC8179AF3744E86CC11921092869842@apache.org>"; start-info="text/xml"; charset=UTF-8259--MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841content-type: application/xop+xml; charset=UTF-8; type="text/xml";content-transfer-encoding: binarycontent-id:
<0....@apache.org>
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header />
<soapenv:Body>
<test1:int_input_outputMessage xmlns:test1=" http://querix.com/xsd">
<test1:param0>10</test1:param0>
</test1:int_input_outputMessage>
</soapenv:Body>
</soapenv:Envelope>--MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841--0
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: re[4]: the problem of enabling MTOM in web service client in AXIS2/C
Posted by donald yang <do...@googlemail.com>.
Hi Dimuthu,
Thanks for your reply. The web services that I wrote are POJO web services.
Then I deploy them into TOMCAT+AXIS2/JAVA 1.2.
best regards
yong
On 10/12/07, Dimuthu Gamage <di...@gmail.com> wrote:
>
> Hi Yong,
>
> I thought your service is generated from WSDL2Java for the soap1.1 port.
> If that is what actually happened you may need to regenerate the service
> with the desired port name.
>
> Thanks
> Dimuthu
>
> On 10/12/07, Yong Yang <y....@querix.com> wrote:
> >
> > Hi Dimuthu,
> >
> > Currently the web service client is written using AXIS2/C 1.0 while the
> > web service is written using AXIS2/JAVA 1.2. I didn't use the generated
> > code from the wsdl. What I have done is to change the soap version from
> > 1.2 to 1.1. Then it works. But I set the soap version to 1.2, it doesn't
> > work even if the wsdl shows that it supports SOAP 1.2.
> >
> > best regards
> > yong
> > >> Hi,
> > >> It seems you have are working on the generated code from the wsdl.
> > In
> > >> WSDL2Java you can provide the port name with -pn option. So
> > regenerate
> > >> the code with the port name.
> >
> > >> Thanks
> > >> Dimuthu
> >
> >
> >
> > >> On 10/12/07, Yong Yang < y.yang@querix.com> wrote: Hi Sahan,
> >
> > >> Thank you very much for your reply.
> >
> > >> When I set the soap version to 1.1, it works fine. Currently I wrote
> > >> the web service using AXIS2/JAVA 1.2 and the generated wsdl has
> > three
> > >> ports, HTTP PORT, SOAP1.1, SOAP1.2. That means the web service
> > server
> > >> also supports SOAP1.2. The question is that it also should work if
> > I set
> > >> the soap version to 1.2 in client size. Is my understanding right?
> > How
> > >> can enable the server support SOAP 1.2?
> >
> > >> best regards
> > >> yong
> >
> > >> >> Hi yong,
> >
> > >> >> In [1] the start-info is "application/soap+xml" (not
> > >> >> "application/xop+xml") and in [3] it is "text/xml". If the
> > request
> > >> >> from Axis2/Java 1.2 works, then my guess is the server requires
> > SOAP
> > >> >> 1.1 and Axis2/C sends SOAP 1.2 by default. Try setting soap
> > version
> > >> to
> > >> >> 1.1 by adding "axis2_options_set_soap_version(options, env,
> > >> >> AXIOM_SOAP11);" to your client code (have a look at
> > >> >> samples/user_guide/clients/echo_blocking_soap11.c)
> >
> > >> >> Thanks
> > >> >> -sahan
> >
> > >> >> On 10/11/07, Yong Yang < y.yang@querix.com> wrote:
> > >> >> > Hi everyone,
> > >> >> >
> > >> >> > I wrote a web service client test case using AXIS2/C 1.0 to
> > access
> > >> a
> > >> >> simple web service. In the client, I have enabled MTOM even if
> > there
> > >> is
> > >> >> no binaary attachment to send in fact. I got one exception(see
> > [1]
> > >> and
> > >> >> [2]).
> > >> >> > Then I compared the soap request created by AXIS2/C 1.0 with
> > the
> > >> soap
> > >> >> request created by AXIS2 1.2. I found the major difference is
> > that
> > >> the
> > >> >> value of start-info is "application/xop+xml" not "text/xml" in
> > the
> > >> soap
> > >> >> request created by AXIS2/C. Is there any API to set the
> > start-info?
> > >> if
> > >> >> not, how can I solve this issue? Many thanks in advance.
> > >> >> >
> > >> >> > best regards
> > >> >> > yong
> > >> >> >
> >
> >
> >
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: axis-c-user-help@ws.apache.org
> >
> >
> >
> >
> >
> >
> > Yong Yang
> > ____________________________________________________________________
> > Contact Details:
> > Querix (UK) - 50, The Avenue, SO17 1XQ, Southampton, UK, Tel+44 2380
> > 232345 Fax: +44 2380 399 685
> > Querix(US) - 8174 S. Holly Street, #225, Centennial, CO 80122-4004, USA,
> > Tel: +1 1-866-732-0389
> >
> > _________________________________________________________________________________
> > QUERIX (UK) Ltd. with registered offices at 5 St. Denys, Portswood
> > Southampton SO2 16N
> > UK Registration Number: 2984439
> > _________________________________________________________________________________
> >
> > Contact: Company: ContactID: 2817 -
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-user-help@ws.apache.org
> >
> >
>
Re: re[4]: the problem of enabling MTOM in web service client in AXIS2/C
Posted by Dimuthu Gamage <di...@gmail.com>.
Hi Yong,
I thought your service is generated from WSDL2Java for the soap1.1 port.
If that is what actually happened you may need to regenerate the service
with the desired port name.
Thanks
Dimuthu
On 10/12/07, Yong Yang <y....@querix.com> wrote:
>
> Hi Dimuthu,
>
> Currently the web service client is written using AXIS2/C 1.0 while the
> web service is written using AXIS2/JAVA 1.2. I didn't use the generated
> code from the wsdl. What I have done is to change the soap version from
> 1.2 to 1.1. Then it works. But I set the soap version to 1.2, it doesn't
> work even if the wsdl shows that it supports SOAP 1.2.
>
> best regards
> yong
> >> Hi,
> >> It seems you have are working on the generated code from the wsdl. In
> >> WSDL2Java you can provide the port name with -pn option. So regenerate
> >> the code with the port name.
>
> >> Thanks
> >> Dimuthu
>
>
>
> >> On 10/12/07, Yong Yang <y....@querix.com> wrote: Hi Sahan,
>
> >> Thank you very much for your reply.
>
> >> When I set the soap version to 1.1, it works fine. Currently I wrote
> >> the web service using AXIS2/JAVA 1.2 and the generated wsdl has three
> >> ports, HTTP PORT, SOAP1.1, SOAP1.2. That means the web service server
> >> also supports SOAP1.2. The question is that it also should work if I
> set
> >> the soap version to 1.2 in client size. Is my understanding right? How
> >> can enable the server support SOAP 1.2?
>
> >> best regards
> >> yong
>
> >> >> Hi yong,
>
> >> >> In [1] the start-info is "application/soap+xml" (not
> >> >> "application/xop+xml") and in [3] it is "text/xml". If the request
> >> >> from Axis2/Java 1.2 works, then my guess is the server requires
> SOAP
> >> >> 1.1 and Axis2/C sends SOAP 1.2 by default. Try setting soap
> version
> >> to
> >> >> 1.1 by adding "axis2_options_set_soap_version(options, env,
> >> >> AXIOM_SOAP11);" to your client code (have a look at
> >> >> samples/user_guide/clients/echo_blocking_soap11.c)
>
> >> >> Thanks
> >> >> -sahan
>
> >> >> On 10/11/07, Yong Yang < y.yang@querix.com> wrote:
> >> >> > Hi everyone,
> >> >> >
> >> >> > I wrote a web service client test case using AXIS2/C 1.0 to
> access
> >> a
> >> >> simple web service. In the client, I have enabled MTOM even if
> there
> >> is
> >> >> no binaary attachment to send in fact. I got one exception(see [1]
> >> and
> >> >> [2]).
> >> >> > Then I compared the soap request created by AXIS2/C 1.0 with the
> >> soap
> >> >> request created by AXIS2 1.2. I found the major difference is
> that
> >> the
> >> >> value of start-info is "application/xop+xml" not "text/xml" in the
> >> soap
> >> >> request created by AXIS2/C. Is there any API to set the
> start-info?
> >> if
> >> >> not, how can I solve this issue? Many thanks in advance.
> >> >> >
> >> >> > best regards
> >> >> > yong
> >> >> >
>
>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
>
>
>
>
> Yong Yang
> ____________________________________________________________________
> Contact Details:
> Querix (UK) - 50, The Avenue, SO17 1XQ, Southampton, UK, Tel+44 2380
> 232345 Fax: +44 2380 399 685
> Querix(US) - 8174 S. Holly Street, #225, Centennial, CO 80122-4004, USA,
> Tel: +1 1-866-732-0389
>
> _________________________________________________________________________________
> QUERIX (UK) Ltd. with registered offices at 5 St. Denys, Portswood
> Southampton SO2 16N
> UK Registration Number: 2984439
>
> _________________________________________________________________________________
> Contact: Company: ContactID: 2817 -
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
re[4]: the problem of enabling MTOM in web service client in AXIS2/C
Posted by Yong Yang <y....@querix.com>.
Hi Dimuthu,
Currently the web service client is written using AXIS2/C 1.0 while the web service is written using AXIS2/JAVA 1.2. I didn't use the generated code from the wsdl. What I have done is to change the soap version from 1.2 to 1.1. Then it works. But I set the soap version to 1.2, it doesn't work even if the wsdl shows that it supports SOAP 1.2.
best regards
yong
>> Hi,
>> It seems you have are working on the generated code from the wsdl. In
>> WSDL2Java you can provide the port name with -pn option. So regenerate
>> the code with the port name.
>> Thanks
>> Dimuthu
>> On 10/12/07, Yong Yang <y....@querix.com> wrote: Hi Sahan,
>> Thank you very much for your reply.
>> When I set the soap version to 1.1, it works fine. Currently I wrote
>> the web service using AXIS2/JAVA 1.2 and the generated wsdl has three
>> ports, HTTP PORT, SOAP1.1, SOAP1.2. That means the web service server
>> also supports SOAP1.2. The question is that it also should work if I set
>> the soap version to 1.2 in client size. Is my understanding right? How
>> can enable the server support SOAP 1.2?
>> best regards
>> yong
>> >> Hi yong,
>> >> In [1] the start-info is "application/soap+xml" (not
>> >> "application/xop+xml") and in [3] it is "text/xml". If the request
>> >> from Axis2/Java 1.2 works, then my guess is the server requires SOAP
>> >> 1.1 and Axis2/C sends SOAP 1.2 by default. Try setting soap version
>> to
>> >> 1.1 by adding "axis2_options_set_soap_version(options, env,
>> >> AXIOM_SOAP11);" to your client code (have a look at
>> >> samples/user_guide/clients/echo_blocking_soap11.c)
>> >> Thanks
>> >> -sahan
>> >> On 10/11/07, Yong Yang < y.yang@querix.com> wrote:
>> >> > Hi everyone,
>> >> >
>> >> > I wrote a web service client test case using AXIS2/C 1.0 to access
>> a
>> >> simple web service. In the client, I have enabled MTOM even if there
>> is
>> >> no binaary attachment to send in fact. I got one exception(see [1]
>> and
>> >> [2]).
>> >> > Then I compared the soap request created by AXIS2/C 1.0 with the
>> soap
>> >> request created by AXIS2 1.2. I found the major difference is that
>> the
>> >> value of start-info is "application/xop+xml" not "text/xml" in the
>> soap
>> >> request created by AXIS2/C. Is there any API to set the start-info?
>> if
>> >> not, how can I solve this issue? Many thanks in advance.
>> >> >
>> >> > best regards
>> >> > yong
>> >> >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-user-help@ws.apache.org
Yong Yang
____________________________________________________________________
Contact Details:
Querix (UK) - 50, The Avenue, SO17 1XQ, Southampton, UK, Tel+44 2380 232345 Fax: +44 2380 399 685
Querix(US) - 8174 S. Holly Street, #225, Centennial, CO 80122-4004, USA, Tel: +1 1-866-732-0389
_________________________________________________________________________________
QUERIX (UK) Ltd. with registered offices at 5 St. Denys, Portswood Southampton SO2 16N
UK Registration Number: 2984439
_________________________________________________________________________________
Contact: Company: ContactID: 2817 -
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: re[2]: the problem of enabling MTOM in web service client in AXIS2/C
Posted by Dimuthu Gamage <di...@gmail.com>.
Hi,
It seems you have are working on the generated code from the wsdl. In
WSDL2Java you can provide the port name with -pn option. So regenerate the
code with the port name.
Thanks
Dimuthu
On 10/12/07, Yong Yang <y....@querix.com> wrote:
>
> Hi Sahan,
>
> Thank you very much for your reply.
>
> When I set the soap version to 1.1, it works fine. Currently I wrote
> the web service using AXIS2/JAVA 1.2 and the generated wsdl has three
> ports, HTTP PORT, SOAP1.1, SOAP1.2. That means the web service server also
> supports SOAP1.2. The question is that it also should work if I set the
> soap version to 1.2 in client size. Is my understanding right? How can
> enable the server support SOAP 1.2?
>
> best regards
> yong
>
> >> Hi yong,
>
> >> In [1] the start-info is "application/soap+xml" (not
> >> "application/xop+xml") and in [3] it is "text/xml". If the request
> >> from Axis2/Java 1.2 works, then my guess is the server requires SOAP
> >> 1.1 and Axis2/C sends SOAP 1.2 by default. Try setting soap version to
> >> 1.1 by adding "axis2_options_set_soap_version(options, env,
> >> AXIOM_SOAP11);" to your client code (have a look at
> >> samples/user_guide/clients/echo_blocking_soap11.c)
>
> >> Thanks
> >> -sahan
>
> >> On 10/11/07, Yong Yang <y....@querix.com> wrote:
> >> > Hi everyone,
> >> >
> >> > I wrote a web service client test case using AXIS2/C 1.0 to access a
> >> simple web service. In the client, I have enabled MTOM even if there
> is
> >> no binaary attachment to send in fact. I got one exception(see [1] and
> >> [2]).
> >> > Then I compared the soap request created by AXIS2/C 1.0 with the
> soap
> >> request created by AXIS2 1.2. I found the major difference is that the
> >> value of start-info is "application/xop+xml" not "text/xml" in the
> soap
> >> request created by AXIS2/C. Is there any API to set the start-info? if
> >> not, how can I solve this issue? Many thanks in advance.
> >> >
> >> > best regards
> >> > yong
> >> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
re[2]: the problem of enabling MTOM in web service client in AXIS2/C
Posted by Yong Yang <y....@querix.com>.
Hi Sahan,
Thank you very much for your reply.
When I set the soap version to 1.1, it works fine. Currently I wrote the web service using AXIS2/JAVA 1.2 and the generated wsdl has three ports, HTTP PORT, SOAP1.1, SOAP1.2. That means the web service server also supports SOAP1.2. The question is that it also should work if I set the soap version to 1.2 in client size. Is my understanding right? How can enable the server support SOAP 1.2?
best regards
yong
>> Hi yong,
>> In [1] the start-info is "application/soap+xml" (not
>> "application/xop+xml") and in [3] it is "text/xml". If the request
>> from Axis2/Java 1.2 works, then my guess is the server requires SOAP
>> 1.1 and Axis2/C sends SOAP 1.2 by default. Try setting soap version to
>> 1.1 by adding "axis2_options_set_soap_version(options, env,
>> AXIOM_SOAP11);" to your client code (have a look at
>> samples/user_guide/clients/echo_blocking_soap11.c)
>> Thanks
>> -sahan
>> On 10/11/07, Yong Yang <y....@querix.com> wrote:
>> > Hi everyone,
>> >
>> > I wrote a web service client test case using AXIS2/C 1.0 to access a
>> simple web service. In the client, I have enabled MTOM even if there is
>> no binaary attachment to send in fact. I got one exception(see [1] and
>> [2]).
>> > Then I compared the soap request created by AXIS2/C 1.0 with the soap
>> request created by AXIS2 1.2. I found the major difference is that the
>> value of start-info is "application/xop+xml" not "text/xml" in the soap
>> request created by AXIS2/C. Is there any API to set the start-info? if
>> not, how can I solve this issue? Many thanks in advance.
>> >
>> > best regards
>> > yong
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: the problem of enabling MTOM in web service client in AXIS2/C
Posted by Sahan Gamage <sa...@gmail.com>.
Hi yong,
In [1] the start-info is "application/soap+xml" (not
"application/xop+xml") and in [3] it is "text/xml". If the request
from Axis2/Java 1.2 works, then my guess is the server requires SOAP
1.1 and Axis2/C sends SOAP 1.2 by default. Try setting soap version to
1.1 by adding "axis2_options_set_soap_version(options, env,
AXIOM_SOAP11);" to your client code (have a look at
samples/user_guide/clients/echo_blocking_soap11.c)
Thanks
-sahan
On 10/11/07, Yong Yang <y....@querix.com> wrote:
> Hi everyone,
>
> I wrote a web service client test case using AXIS2/C 1.0 to access a simple web service. In the client, I have enabled MTOM even if there is no binaary attachment to send in fact. I got one exception(see [1] and [2]).
> Then I compared the soap request created by AXIS2/C 1.0 with the soap request created by AXIS2 1.2. I found the major difference is that the value of start-info is "application/xop+xml" not "text/xml" in the soap request created by AXIS2/C. Is there any API to set the start-info? if not, how can I solve this issue? Many thanks in advance.
>
> best regards
> yong
>
> [1] soap request created by axis2/c
>
> POST /axis2/services/simple_int HTTP/1.1
> User-Agent: Axis2/C
> Content-Length: 555
> Content-Type: multipart/related; boundary=MIMEBoundaryc4bffdc7-918b-40ee-bacf-9ce9962d479b; type="application/xop+xml"; start="< 0.10302e03-c3be-422f-b33b-a8a2a4880a6f@apache.org>"; start-info="application/soap+xml"; charset="UTF-8";action=""""
> Host: 127.0.0.1:9000
> --MIMEBoundaryc4bffdc7-918b-40ee-bacf-9ce9962d479b
> content-transfer-encoding: binary
> content-id: < 0.10302e03-c3be-422f-b33b-a8a2a4880a6f@apache.org>content-type: application/xop+xml; charset=UTF-8; type="application/soap+xml";
> <soapenv:Envelope xmlns:soapenv=" http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header></soapenv:Header>
> <soapenv:Body>
> <ns1:int_input_outputMessage xmlns:ns1=" http://querix.com/xsd">
> <param0>10</param0>
> </ns1:int_input_outputMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryc4bffdc7-918b-40ee-bacf-9ce9962d479b--
>
> [2] soap reply for the soap request created by axis2/c
>
> HTTP/1.1 400 Bad Request
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml; action=" http://www.w3.org/2005/08/addressing/soap/fault";charset=UTF-8
> Transfer-Encoding: chunked
> Date: Thu, 11 Oct 2007 13:24:51 GMT
> Connection: close
> 241
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope ">
> <soapenv:Header>
> <wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">Invalid Content Type Field in the Mime Message</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail></soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
> [3] soap request created by AXIS2 java
>
> POST /axis2/services/simple_int HTTP/1.1
> SOAPAction: "urn:int_input_output"
> User-Agent: Axis2
> Host: 127.0.0.1:9000
> Transfer-Encoding: chunked
> Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841; type="application/xop+xml"; start="< 0.urn:uuid:0CC8179AF3744E86CC11921092869842@apache.org>"; start-info="text/xml"; charset=UTF-8259--MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841content-type: application/xop+xml; charset=UTF-8; type="text/xml";content-transfer-encoding: binarycontent-id:
> <0....@apache.org>
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <test1:int_input_outputMessage xmlns:test1=" http://querix.com/xsd">
> <test1:param0>10</test1:param0>
> </test1:int_input_outputMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841--0
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org