You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/12/15 04:18:18 UTC
[jira] Resolved: (CXF-2035) Issues with SOAPAction
[ https://issues.apache.org/jira/browse/CXF-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2035.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.6
2.1.9
> Issues with SOAPAction
> -----------------------
>
> Key: CXF-2035
> URL: https://issues.apache.org/jira/browse/CXF-2035
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.1.3
> Reporter: Adrian Corcoran
> Assignee: Daniel Kulp
> Fix For: 2.1.9, 2.2.6
>
>
> It would appear that there are issues with the usage of both the HTTP SOAPAction & WSA SOAP action:
> If for the sake of arguments we have a web service with 2 operations create & delete and with corresponding soap actions the following behaviour is observed.
> 1. If I specify a HTTP SOAP Action of create but the body of the soap request corresponds to a deleteRequest my create operation is invoked
> 2. If I specify a WSA SOAP Action of create but the body of the soap request corresponds to a deleteRequest my delete operation is invoked
> See http://www.nabble.com/ws-a-questions-td21788455.html#a21788455 for the discussion on this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.