We are interested in backporting RESTEASY-2648 to 3.15.x. In the JIRA
 there was a discussion about backporting to 3.13.x but it looks like
this never happened. We are interested in RESTEASY-2648 because we would
like to get rid of the Guava dependency when using the Jackson 2
provider in a Java SE environment. We are still on 3.15.x because we are
using RESTEasy both in WildFly and in Java SE and we would like to keep
the versions in sync, and WildFly is still on 3.15.x.
Is this something you would be acceptable? If so we would be willing to
work on a PR. What would be involved other than cherry picking the
commit , cloning the JIRA and opening a PR?
we are looking for guidance for an activity related to Apicurio projects that are writing a Quarkus based app leveraging RestEasy.
We have been asked to customize the default error responses, like the following:
`reason: "javax.ws.rs.NotAllowedException: RESTEASY003650: No resource method found for DELETE, return 405 with Allow header"`
So to have them translated to business-specific messages.
We have successfully used Exception mappers are application layer, but it seems that if an error comes from the platform then the application's exception mapper is not called. So for things like authentication failures, or when trying to access an API endpoint that doesn't exist, or calling an existing API with the wrong Content-Type - these are Reasteasy errors that don't go through the mapper.
We are thus consulting the experts here to understand what is supposed to be to idiomatic way to obtain this in RestEasy?