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

nadir amra resolved AXIS2-3090.
-------------------------------

    Resolution: Fixed

I hope I am not stepping on any toes, but I have resolved this issue.  Deepal, 
please accept my apologies if I am not doing this according to some process due 
to my handling the issue that is not assigned to me.

Basically added following in axis2.xml:

    
<!-- Following parameter will suppress generation of SOAP 1.2 bindings in 
auto-generated WSDL files -->
<parameter name="disableSOAP12" locked="true">false</parameter>

If set to true, not SOAP 1.2 bindings will be generated, for both wsdl and 
wsdl2.  

Of course this issue supplements issue AXIS2-3114.  That is,  AXIS2-3114 still 
needs to be implemented to give more flexibility.

> Make SOAP 1.2 bindings optional, as they break older Axis 1 clients
> -------------------------------------------------------------------
>
>                 Key: AXIS2-3090
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3090
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 1.2
>            Reporter: Thomas Leonard
>            Assignee: Deepal Jayasinghe
>             Fix For: nightly
>
>         Attachments: disable-soap-1.1.patch
>
>
> We're trying to create some Axis 2 services which are usable by other clients 
> (including .NET and Axis 1). At first, we had problems due to AXIS2-2294, but 
> upgrading to Axis 2 1.3-RC2 fixed that. However, the WSDL is still unreadable 
> to the Axis 1 client because of the SOAP 1.2 bindings which are also present 
> in the file:
> java.io.IOException: ERROR: Missing <soap:fault> element inFault 
> "XMLStreamException" in operation "XMLStreamException", in binding sayHello
> The attached patch (disable-soap-1.1.patch) adds a configuration option to 
> disable generation of these bindings.

-- 
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