Skip to content

Always consider @RegisterRestClient interface as REST Clients #47508

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented Apr 23, 2025

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.

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.
Copy link

quarkus-bot bot commented Apr 23, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit aab7682.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants