cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-6678) AsyncResponse & outFaultInterceptors
Date Mon, 16 Nov 2015 21:49:11 GMT

    [ https://issues.apache.org/jira/browse/CXF-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007404#comment-15007404
] 

Sergey Beryozkin commented on CXF-6678:
---------------------------------------

Hi, if you are not sure then it makes sense asking at the CXF users list.

In this case I'd say it is a won't fix. There's really no requirement to link JAX-RS 2.0 AsyncResponse
with CXF out fault interceptors. Please use ExceptionMapper to manage these exceptions 


> AsyncResponse & outFaultInterceptors
> ------------------------------------
>
>                 Key: CXF-6678
>                 URL: https://issues.apache.org/jira/browse/CXF-6678
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.0.2
>         Environment: karaf 3.0.4
>            Reporter: Alberto São Marcos
>            Priority: Minor
>
> With an _AbstractPhaseInterceptor_ implementation configured as an _outFaultInterceptors_,
its _handleMessage_  does not get invoked when an _Exception_ is returned by the _AsyncResponse.resume_
method.
> The response does arrive with a 500 response code, but the interceptor does not seem
to be invoked at all.
> Not sure if a bug or just a know limitation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message