ExceptionMappers should be implemented by the users not by the library about jackson-jaxrs-providers HOT 5 CLOSED

I suggest you bring this up on mailing list -- for backwards compatibility, simple removal is not an option, there needs to be a graceful way to upgrade. Improvements to handling (especailly via pull requests) are welcome too of course.

from jackson-jaxrs-providers.

You should be able to unregister the Jackson ExceptionMappers in your Jersey configuration in the meantime.

from jackson-jaxrs-providers.

Thanks for your response, I will try to unregister the exception mapper if
such a thing is possible, never done that before.

On 4 July 2014 12:05, Paul Brown [email protected] wrote:

You should be able to unregister the Jackson ExceptionMappers in your
Jersey configuration in the meantime.

—
Reply to this email directly or view it on GitHub
#53 (comment)
.

from jackson-jaxrs-providers.

Actually as far as I found in my research it is not possible to unregister
an exception mapper in Jersey, another work-around could be to register
manually the jackson provider instead of the jackson feature in Jersey.
Some people in Internet recommend doing that, but the Jersey documentation
recommends to use the org.glassfish.jersey.jackson.JacksonFeature.class
which is the one that registers the mappers that I want to get rid of. So
that is the dilemma.

On 5 July 2014 00:45, Ramiro Serrato [email protected] wrote:

Thanks for your response, I will try to unregister the exception mapper if
such a thing is possible, never done that before.

On 4 July 2014 12:05, Paul Brown [email protected] wrote:

You should be able to unregister the Jackson ExceptionMappers in your
Jersey configuration in the meantime.

—
Reply to this email directly or view it on GitHub
#53 (comment)
.

from jackson-jaxrs-providers.

I think this is dup of #22

from jackson-jaxrs-providers.