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/23 03:37:22 UTC

[jira] Commented: (CXF-283) Support SOAPAction header

    [ 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