Built-in RestDataPanacheExceptionMapper is not overridable or has higher priority about quarkus

[slgobinath]

Thanks @geoand
Switching to quarkus-resteasy-reactive-jackson does fix the problem. Feel free to close this issue or edit it to quarkus-resteasy-jackson specific.

[quarkus-bot]

/cc @FroMage (panache), @loicmathieu (panache)

[geoand]

Can you please attach a sample application that behaves as you mention, as I tried to reproduce this and it worked as expected.

Thanks

[slgobinath]

Hi @geoand , Thanks for the quick response.
I've created the new project here https://github.com/slgobinath/issue-38799
Here's the link to core classes:

• PanacheEntityResource: FooResource
• ExceptionMapper: RestDataPanacheExceptionMapper - If this class is picked up the response code must be 400 and the test will pass. Instead, if the built-in mapper is used, 500 status code will be returned and the test will fail.
• Test class: FooResourceTest

While playing with it more I came across an interesting case.
Setting @Priority(1) to [RestDataPanacheExceptionMapper.java#L12] fixes the problem which makes sense to me - Is this is the expected behavior? I'm new to Quarkus so not sure if all custom mappers must have an explicit priority set.

However, moving the RestDataPanacheExceptionMapper class to the com.example.config package also fixes the problem which I don't know how. Again, I'm new to Quarkus so not sure if this is an expected behavior but as a novice Quarkus user, I expected it to work regardless of the location (aka package) of the class.

[geoand]

I am not sure what the problem is, but if you use quarkus-resteasy-reactive-jackson (as we recommend) instead of quarkus-resteasy-jackson, then everything works as expected