You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "jimma (JIRA)" <ji...@apache.org> on 2011/04/18 15:15:05 UTC

[jira] [Created] (CXF-3458) AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message

AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message 
---------------------------------------------------------------------------------------------------------------

                 Key: CXF-3458
                 URL: https://issues.apache.org/jira/browse/CXF-3458
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 2.3.4, 2.4
            Reporter: jimma
            Assignee: jimma
             Fix For: 2.4.1, 2.3.5


Refactor in the MAPAggregator interceptor: if the wsa header is not asserted for the ws addressing required client, the fault should be generated directly in MAPAggregator. It does not need to do it in PolicyVerficationIntecettor.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3458) AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message

Posted by "jimma (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jimma resolved CXF-3458.
------------------------

    Resolution: Fixed

> AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message 
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-3458
>                 URL: https://issues.apache.org/jira/browse/CXF-3458
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4, 2.3.4
>            Reporter: jimma
>            Assignee: jimma
>             Fix For: 2.4.1, 2.3.5
>
>
> Refactor in the MAPAggregator interceptor: if the wsa header is not asserted for the ws addressing required client, the fault should be generated directly in MAPAggregator. It does not need to do it in PolicyVerficationIntecettor.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira