Always consider @RegisterRestClient interface as REST Clients #47508
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.
In RESTEasy Classic, even when an interface is annotated with @RegisterRestClient, the interface is not considered a REST Client if it has implementations.
It is not consistent with Quarkus REST and is annoying when you have both the client and the server parts in the same application.
It was reported by a user here: https://quarkusio.zulipchat.com/#narrow/channel/187030-users/topic/Synthetic.20bean.20generation.20for.20.40RestClient/with/513892718 .
And I think the intention is pretty clear when you have an explicit
@RegisterRestClient
annotation.