[
https://issues.apache.org/jira/browse/AXIS2-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486771
]
Steven E. Harris commented on AXIS2-2463:
-----------------------------------------
Good, we settled the typo problem. Now the question arises: Should AXIS2 always
use SOAP 1.1 by default, even when the WSDL parsed to generate the stubs
indicated that it's bound to SOAP 1.2? I think the generated stub should take
whatever steps are necessary to enable the proper SOAP version specified in the
motivating WSDL document.
> WSDL 2 bindings to SOAP 1.2 over HTTP should cause ServiceClient to use SOAP
> 1.2 by default
> -------------------------------------------------------------------------------------------
>
> Key: AXIS2-2463
> URL: https://issues.apache.org/jira/browse/AXIS2-2463
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
> Affects Versions: nightly
> Environment: N/A
> Reporter: Steven E. Harris
> Assigned To: Keith Godwin Chapman
> Priority: Minor
>
> Per the discussion at
> Getting client stub to use SOAP version 1.2
> http://thread.gmane.org/gmane.comp.apache.webservices.axis.user/54837
> when a WSDL 2.0 file specifies a binding to SOAP 1.2 over HTTP with the
> attribute
> wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";
> the AXIS2 WSDL2Java program (or whatever else is involved) should force the
> generate stub's ServiceClient to use SOAP 1.2 by default, rather than SOAP
> 1.1 as it does now.
> The workaround at present is to call
> stub._getServiceClient().getOptions().
> setSoapVersionURI(
> org.apache.axiom.soap.SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI );
> but that step should not be necessary.
--
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]
