eclipse-ee4j / eclipse-ee4j/jersey

Default Exception Mapper Related Question

Open
#5,743 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
730
Forks
382
PR merge metrics
No merged PRs in 30d

Description

I migrated my application from jersey 2.x to 3.x along with spring boot. Previously when I throw any `RuntimeException`, the errors will be mapped to **MappableException class** and processed. But after migration to 3.1.8, it seems the exceptions are not mapped properly and I can see the error log `org.glassfish.jersey.server.ServerRuntime$Responder - An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper.
java.lang.IllegalArgumentException: Invalid format: " "`

Is there any other way to implement it or is it a bug?

cc: @jansupol

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.