[jira] Updated: (CXF-3260) JAX-RS: org.apache.cxf.jaxrs.utils.Messages properties file missing definition for NO_CRI_MATCH

["Glen Mazza (JIRA)" <ji...@apache.org>]

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

Glen Mazza updated CXF-3260:
----------------------------

      Component/s: JAX-RS
    Fix Version/s:     (was: 2.3.3)
                   2.4
         Assignee: Glen Mazza

Fixed on 2.3.x and 2.4.x branches--thanks!

Glen

> JAX-RS: org.apache.cxf.jaxrs.utils.Messages properties file missing definition for NO_CRI_MATCH
> -----------------------------------------------------------------------------------------------
>
>                 Key: CXF-3260
>                 URL: https://issues.apache.org/jira/browse/CXF-3260
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.3.1
>         Environment: Java 1.6
> CXF 2.3.1 / CXF 2.3.2
>            Reporter: Ka-Lok Fung
>            Assignee: Glen Mazza
>            Priority: Minor
>             Fix For: 2.4
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> JAXRSUtils.selectResourceClass expects a message keyed by "NO_CRI_MATCH". However, when you look in the Messages properties file (org.apache.cxf.jaxrs.utils.Messages), it is absent.
> Because this message is absent, the Java runtime needlessly generates a ResourceNotFound exception for every resource in your application that it examined and couldn't match the incoming method.
> The suggested fix, is of course, to define that string. Here's what I came up with:
> NO_CRI_MATCH=Resource class {1} will not be selected, request path : {0}

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