You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dan Diephouse (JIRA)" <ji...@apache.org> on 2006/12/02 22:46:20 UTC
[jira] Created: (CXF-283) Support SOAPAction header
Support SOAPAction header
-------------------------
Key: CXF-283
URL: http://issues.apache.org/jira/browse/CXF-283
Project: CXF
Issue Type: New Feature
Affects Versions: 2.0-M1
Reporter: Dan Diephouse
Fix For: 2.0-RC
We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (CXF-283) Support SOAPAction header
Posted by "tli (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-283?page=all ]
tli resolved CXF-283.
---------------------
Fix Version/s: 2.0
(was: 2.0-RC)
Resolution: Fixed
> Support SOAPAction header
> -------------------------
>
> Key: CXF-283
> URL: http://issues.apache.org/jira/browse/CXF-283
> Project: CXF
> Issue Type: New Feature
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Assigned To: tli
> Fix For: 2.0
>
>
> We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (CXF-283) Support SOAPAction header
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-283?page=all ]
Dan Diephouse reopened CXF-283:
-------------------------------
Reopening as
1. There is no test which actually tests this over HTTP
2. The current interceptor doesn't set the SOAPAction header on the outgoing response as far as I can see, and I believe this is required.
> Support SOAPAction header
> -------------------------
>
> Key: CXF-283
> URL: http://issues.apache.org/jira/browse/CXF-283
> Project: CXF
> Issue Type: New Feature
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Assigned To: tli
> Fix For: 2.0
>
>
> We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CXF-283) Support SOAPAction header
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-283:
----------------------------
Component/s: Soap Binding
Fix Version/s: (was: 2.0)
2.0-RC
Assignee: maomaode (was: tli)
Affects Version/s: (was: 2.0-M1)
2.0-RC
> Support SOAPAction header
> -------------------------
>
> Key: CXF-283
> URL: https://issues.apache.org/jira/browse/CXF-283
> Project: CXF
> Issue Type: New Feature
> Components: Soap Binding
> Affects Versions: 2.0-RC
> Reporter: Dan Diephouse
> Assigned To: maomaode
> Fix For: 2.0-RC
>
>
> We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-283) Support SOAPAction header
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-283?page=comments#action_12460631 ]
Dan Diephouse commented on CXF-283:
-----------------------------------
I take back #2, it does seem to do this. Is there a system test that I'm missing on #1? I'd just like to be doubly sure this works when everything is integrated...
> Support SOAPAction header
> -------------------------
>
> Key: CXF-283
> URL: http://issues.apache.org/jira/browse/CXF-283
> Project: CXF
> Issue Type: New Feature
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Assigned To: tli
> Fix For: 2.0
>
>
> We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (CXF-283) Support SOAPAction header
Posted by "tli (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-283?page=all ]
tli reassigned CXF-283:
-----------------------
Assignee: tli
> Support SOAPAction header
> -------------------------
>
> Key: CXF-283
> URL: http://issues.apache.org/jira/browse/CXF-283
> Project: CXF
> Issue Type: New Feature
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Assigned To: tli
> Fix For: 2.0-RC
>
>
> We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CXF-283) Support SOAPAction header
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse closed CXF-283.
-----------------------------
Resolution: Fixed
> Support SOAPAction header
> -------------------------
>
> Key: CXF-283
> URL: https://issues.apache.org/jira/browse/CXF-283
> Project: CXF
> Issue Type: New Feature
> Components: Soap Binding
> Affects Versions: 2.0-RC
> Reporter: Dan Diephouse
> Assigned To: maomaode
> Fix For: 2.0-RC
>
>
> We should support the SOAPAction header for resolving operations. This can be done through an additional SOAPActionInInterceptor which selects the appropriate operation from a Service based on the header. Note that we also need a SOAPActionOutInterceptor to set it on outgoing messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.