RESTEasy Reactive Client: propagate declared exceptions #48291
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RESTEasy Reactive Client generates a
$$CDIWrapper
class for each MP RestClient interface, which is then discovered by ArC. The generated classes however used to not declare any exceptions on methods, even if the interface did declare some. This is wrong at least in case the bean is intercepted (for example using MP Fault Tolerance), because undeclared checked exceptions are wrapped intoArcUndeclaredThrowableException
by interception subclasses. This commit fixes that by propagating all exception types from the interface methods to the$$CDIWrapper
methods.Fixes #48286