You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/01/31 15:56:10 UTC

[jira] [Resolved] (CXF-5534) ProviderFactory returns incorrect ExceptionMapper when no exact match is registered

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

Sergey Beryozkin resolved CXF-5534.
-----------------------------------

    Resolution: Fixed
      Assignee: Sergey Beryozkin

> ProviderFactory returns incorrect ExceptionMapper when no exact match is registered
> -----------------------------------------------------------------------------------
>
>                 Key: CXF-5534
>                 URL: https://issues.apache.org/jira/browse/CXF-5534
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.8
>            Reporter: Hans Weisheimer
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 2.7.9
>
>         Attachments: ProviderFactoryExceptionMapperTest.java
>
>
> The JAX-RS 1.1 spec says:
> When choosing an exception mapping provider to map an exception, an implementation MUST use the provider whose generic type is the nearest superclass of the exception.
> In 2.7.0, this was working per the spec.  In 2.7.8 (likely starting with 2.7.6, but not tested), the FIRST ExceptionMapper provider is returned when there is no exact match.  This usually results in a ClassCastException.
> In the attached test, a NullPointerException should map to the registered ExceptionMapper<RuntimeException> provider, but it does not.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)