Re: WebApplicationExceptionMapper not being called

2019-12-26 Thread Andriy Redko
Thank you, agree with Romain, looks like an issue to me, please open one. IJF> The issue was the DefaultExceptionMapper that I created that extends WebApplicationExceptionMapper was never IJF> called. Also WebApplicationExceptionMapper was never called if I didn't create the default one.

Re: WebApplicationExceptionMapper not being called

2019-12-26 Thread Andriy Redko
Hi Ivan, Please correct me if I misunderstood the case > Hello guys, I am trying to log the exception thrown by > WebApplicationExceptionMapper but the exception mapper is never called. You have an exception mapper (WebApplicationExceptionMapper) which throws (possibly, another) exception

Re: WebApplicationExceptionMapper not being called

2019-12-25 Thread Romain Manni-Bucau
Hi Ivan You can set it with a cxf interceptor or even jaxrs filter but looks like a bug, at least the default. Default should be true only if there is no custom mapper, not if there is any registered mapper matching and this is known at deploy time. Guess you should open a ticket. Le mer. 25

Re: WebApplicationExceptionMapper not being called

2019-12-25 Thread Ivan Junckes Filho
It seems the issue is with: wae.spec.optimization property, it needs to be false or it webapplicationexception will be skipped. But I can't find the way to set it to false. Property is part of org.apache.cxf.message.Message. Anyone can help? system.properties didn't work. On Wed, Dec 25, 2019

WebApplicationExceptionMapper not being called

2019-12-25 Thread Ivan Junckes Filho
Hello guys, I am trying to log the exception thrown by WebApplicationExceptionMapper but the exception mapper is never called. Instead of calling it tomee calls ExceptionUtils.convertFaultToResponse. Even writing a new default exception mapper doesn't work. Anyone knows how can I print the