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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
