You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andrea Smyth (JIRA)" <ji...@apache.org> on 2007/08/21 13:37:32 UTC

[jira] Resolved: (CXF-364) Make WS-* interceptors resistant to absence of Adressing or RM headers/properties

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

Andrea Smyth resolved CXF-364.
------------------------------

    Resolution: Fixed

This should be fixed by now, certainly for the case of ws-addressing where an optional addressing assertion is handled correctly.

> Make WS-* interceptors resistant to absence of Adressing or RM headers/properties
> ---------------------------------------------------------------------------------
>
>                 Key: CXF-364
>                 URL: https://issues.apache.org/jira/browse/CXF-364
>             Project: CXF
>          Issue Type: Task
>          Components: WS-* Components
>            Reporter: Andrea Smyth
>
> It is possible that only some operations on an endpoint are reliable/use addressing, whereas others are not. This is the case when the policy in question is attached to the operation or binding operation but not to the service or port type. Although in such a case the addressing or RM interceptors shuld not be in the chain, they at least should cause no harm and simply pass the message through.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.