I noticed that the resteasy implementation did not call a registered ResponseExceptionMapper when subresource interface methods are called; while it works fine for normal resources.
I suggest adding a test for this use-case; and maybe other providers could be tested on subresources as well.
I noticed that the resteasy implementation did not call a registered ResponseExceptionMapper when subresource interface methods are called; while it works fine for normal resources.
I suggest adding a test for this use-case; and maybe other providers could be tested on subresources as well.
See https://github.com/resteasy/resteasy-microprofile/issues/239#issue-2058665792 for the resteasy issue.