You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thomas Leonard (JIRA)" <ji...@apache.org> on 2007/08/07 12:05:59 UTC
[jira] Created: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
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
Fix For: 1.3
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "Richard Taylor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518533 ]
Richard Taylor commented on AXIS2-3090:
---------------------------------------
I believe the author made a simple typo in the name of the attached patch. It should be disable-soap-1.2.patch, not "1.1". Just pointing it out to avoid confusion. I'm also interested in this fix as I'm also having problems with some older clients/tools handling the SOAP 1.2 binding in the WSDLs. There are also tools (Eclipse WTP 2.0 WSDL validator) having issues with the HTTP Binding as well.
> 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: 1.3
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2-3090) Make SOAP 1.2 bindings
optional, as they break older Axis 1 clients
Posted by "Richard Taylor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518533 ]
richt edited comment on AXIS2-3090 at 8/8/07 12:43 PM:
----------------------------------------------------------------
I believe the author made a simple typo in the name of the attached patch. It should be disable-soap-1.2.patch, not "1.1". Just pointing it out to avoid confusion. I'm also interested in this fix as I'm also having problems with some older clients/tools handling the SOAP 1.2 binding in the WSDLs. There are also tools (Eclipse WTP 2.0 WSDL validator) having issues with the HTTP/REST Binding as well.
was (Author: richt):
I believe the author made a simple typo in the name of the attached patch. It should be disable-soap-1.2.patch, not "1.1". Just pointing it out to avoid confusion. I'm also interested in this fix as I'm also having problems with some older clients/tools handling the SOAP 1.2 binding in the WSDLs. There are also tools (Eclipse WTP 2.0 WSDL validator) having issues with the HTTP Binding as well.
> 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: 1.3
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-3090:
-------------------------------------
Fix Version/s: (was: 1.3)
nightly
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-3090:
----------------------------------------
Assignee: Deepal Jayasinghe
> 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: 1.3
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "Thomas Leonard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Leonard updated AXIS2-3090:
----------------------------------
Attachment: disable-soap-1.1.patch
> 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
> Fix For: 1.3
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "nadir amra (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "nadir amra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534478 ]
nadir amra commented on AXIS2-3090:
-----------------------------------
Deepal, you plan on working on this? I can look into this and provide a configuration switch similar to disableRest in axis2.xml config file....
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3090) Make SOAP 1.2 bindings optional, as
they break older Axis 1 clients
Posted by "Thomas Leonard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518665 ]
Thomas Leonard commented on AXIS2-3090:
---------------------------------------
Yes, the patch is badly named - sorry!
> 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: 1.3
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org