cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-3248) JAX-RS (wrongly?) complaining about no resource methods for ExceptionMappers.
Date Sat, 15 Jan 2011 23:14:45 GMT
JAX-RS (wrongly?) complaining about no resource methods for ExceptionMappers.
-----------------------------------------------------------------------------

                 Key: CXF-3248
                 URL: https://issues.apache.org/jira/browse/CXF-3248
             Project: CXF
          Issue Type: Improvement
          Components: JAX-RS
    Affects Versions: 2.3.2
            Reporter: Glen Mazza
            Priority: Minor


Example 7-1 of the JAX-RS book samples (see https://issues.apache.org/jira/browse/CXF-3247)
is returning a unclear error message when it processes the following ExceptionMapper:

@Provider
public class NotFoundExceptionMapper implements ExceptionMapper<NotFoundException>
{
   public Response toResponse(NotFoundException exception)
   {
      return Response.status(Response.Status.NOT_FOUND)
              .entity(exception.getMessage())
              .type("text/plain").build();
   }
}

This is the error message it's returning:
WARNING: No resource methods have been found for resource class com.restfully.shop.services.NotFoundExceptionMapper

I'm not sure why an exception mapper needs to have resource methods, or what a "resource method"
is for that matter.  I think this error is appropriate for root resources only and not exception
mappers, if so, this message should be suppressed for exception mappers.  OTOH, if this warning
does have meaning for exception mappers, could it be made clearer for newbies/novices?

Note this example has other bugs with it, not related to this problem (https://issues.jboss.org/browse/RESTEASY-495).

To duplicate, download and extract RESTEasy and make the pom.xml and web.xml changes all described
in https://issues.apache.org/jira/browse/CXF-3247.  Then just run mvn clean install and you'll
see the above error message.

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


Mime
View raw message