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 <[EMAIL PROTECTED]> 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 < [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] 






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

Reply via email to