Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <129160505.1256737139494.JavaMail.jira@brutus>
Date: Wed, 28 Oct 2009 13:38:59 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Resolved: (CXF-2502) decoupled WS-A and WS-Sec does not
 result in faults back to clients
In-Reply-To: <1104745437.1256677619542.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.