[ 
https://issues.apache.org/jira/browse/AXIS2C-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dimuthu Gamage resolved AXIS2C-1168.
------------------------------------

    Resolution: Fixed

Fixed in the svn. Early I was looking only at soap action. Now it is truly 
fixed :). May be you can try a nightly build tomorrow at 
http://people.apache.org/dist/axis2/nightly


>   WSDL2C.sh is not generating soap 1.2 compliant client stubs for wsdl with 
> soap 1.2 bindings
> ---------------------------------------------------------------------------------------------
>
>                 Key: AXIS2C-1168
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1168
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: code generation
>         Environment: CentOS4.4 on VMWare (windows xp host).
> On axis2/java (1.2/1.3/1.4).
> axis2c 1.4.
>            Reporter: naveen bhat
>            Assignee: Dimuthu Gamage
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> I am using a wsdl with soap 1.2 bindings.I generated
> client stub using three version of axis2/java (1.2/1.3/1.4). In all
> three I found that in the client stub the  call for the operation,let
> say add(for eg) always sets the soap version to AXIS2_SOAP11,but
> actually it should be AXIS2_SOAP12 for a wsdl with soap 1.2 bindings.
> I am not finding any options in WSDL2C tool to generate client code
> for soap 1.2 . I also tried to set the soap version to 1.2 (in main
> function of client) before calling the operation defined in stub ,but
> this did not work as the soap version was reset back to soap 1.1 in
> the stub(let say axis2_stub_op_add() for eg).
> So my question is how do  i use code generator to generate stub which
> can send soap 1.2 compliant message at the client side.
> PS: Following command was used to generate stub
>     WSDL2C.sh -uri <wsdlpath> -d adb -u

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to