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/10/27 22:06:59 UTC

[jira] Created: (CXF-2502) decoupled WS-A and WS-Sec does not result in faults back to clients

decoupled WS-A and WS-Sec does not result in faults back to clients
-------------------------------------------------------------------

                 Key: CXF-2502
                 URL: https://issues.apache.org/jira/browse/CXF-2502
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 2.2.4
            Reporter: Daniel Kulp
            Assignee: Daniel Kulp
             Fix For: 2.2.5



The example in:
https://issues.apache.org/jira/browse/CXF-2489
shows this.

Basically, if an interceptor that lives between MAPCodec and MAPAggregator throws an exception, the fault is sent like a normal response.  However, the client is looking for a partial response and then the fault on the decoupled channel.   Thus, the client never sees the fault and just gets an IOException and/or hangs.



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

[jira] Resolved: (CXF-2502) decoupled WS-A and WS-Sec does not result in faults back to clients

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

Daniel Kulp resolved CXF-2502.
------------------------------

    Resolution: Fixed

> decoupled WS-A and WS-Sec does not result in faults back to clients
> -------------------------------------------------------------------
>
>                 Key: CXF-2502
>                 URL: https://issues.apache.org/jira/browse/CXF-2502
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.2.4
>            Reporter: Daniel Kulp
>            Assignee: Daniel Kulp
>             Fix For: 2.2.5
>
>
> The example in:
> https://issues.apache.org/jira/browse/CXF-2489
> shows this.
> Basically, if an interceptor that lives between MAPCodec and MAPAggregator throws an exception, the fault is sent like a normal response.  However, the client is looking for a partial response and then the fault on the decoupled channel.   Thus, the client never sees the fault and just gets an IOException and/or hangs.

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