axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yong Yang <>
Subject the problem of enabling MTOM in web service client in AXIS2/C
Date Thu, 11 Oct 2007 15:23:19 GMT
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

[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="<>";
start-info="application/soap+xml"; charset="UTF-8";action=""""
content-transfer-encoding: binary
content-id: <>content-type: application/xop+xml;
charset=UTF-8; type="application/soap+xml";
   <soapenv:Envelope xmlns:soapenv="">
         <ns1:int_input_outputMessage xmlns:ns1="">

[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="";charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 11 Oct 2007 13:24:51 GMT
Connection: close
<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:wsa="" xmlns:soapenv="
               <soapenv:Text xml:lang="en-US">Invalid Content Type Field in the Mime

[3] soap request created by AXIS2 java

POST /axis2/services/simple_int HTTP/1.1
SOAPAction: "urn:int_input_output"
User-Agent: Axis2
Transfer-Encoding: chunked
Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_0CC8179AF3744E86CC11921092869841;
type="application/xop+xml"; start="<>";
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:
      <?xml version='1.0' encoding='UTF-8'?>
         <soapenv:Envelope xmlns:soapenv="">
            <soapenv:Header />
               <test1:int_input_outputMessage xmlns:test1="">

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message