tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirys <ki...@neoteroi.org>
Subject Re: WARNING: No operation matching request path on a full jax-rs app
Date Mon, 06 Jun 2016 07:28:55 GMT
I don't think I'll use something different by TomEE so portability isn't 
an issue.
But I would like to figure out why the ExceptionMapper doesn't work, 
maybe it is something that I didn't configure properly.

I'll try to make a demo app that reproduces the issue


On 05/06/2016 21:53, Romain Manni-Bucau wrote:
> The last one should catch it otherwise a Filter wrapping the request is
> likely the easiest. If you don't care staying 100% portable a CXF
> interceptor (or another extension point) does the job pretty well AFAIK
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau>
|
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-06-05 21:42 GMT+02:00 Kirys <kirys@neoteroi.org>:
>
>> On 05/06/2016 21:20, Romain Manni-Bucau wrote:
>>
>>> Did you try an ExceptionMapper? It could handle 404 and delegate others.
>>>
>> tried these two without any result:
>>
>> @Provider
>> public class EntityNotFoundMapper
>>       implements ExceptionMapper<EntityNotFoundException> {
>>
>>     @Override
>>     public Response toResponse(EntityNotFoundException e) {
>>        return Response.status(Response.Status.NOT_FOUND).build();
>>     }
>> }
>>
>>
>> @Provider
>> public class WebApplicationExceptionHandler implements
>> ExceptionMapper<WebApplicationException> {
>>
>>      @Override
>>      public Response toResponse(WebApplicationException e) {
>>          return Response.status(Response.Status.NOT_FOUND).build();
>>      }
>> }
>>
>>


Mime
View raw message