-
Notifications
You must be signed in to change notification settings - Fork 77
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
NOTIF-55 Migrate to resteasy-reactive and rest-client-reactive #202
Conversation
Quarkus quarkusio/quarkus#16577 was fixed as expected, but I found what seems to be a new bug: quarkusio/quarkus#16897 |
I worked around the bug and the build is now successful. Unfortunately, the response time is really bad (500 to 600ms now vs 10 to 100ms before) so I'm trying to figure out why the app is so slow. |
15eab90
to
b51a6af
Compare
|
Rebased on This is ready for a review/merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
@Path("/internal") | ||
@Consumes(APPLICATION_JSON) | ||
@Produces(APPLICATION_JSON) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought this was the default and we didn't need to specify it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is true for quarkus-resteasy
but apparently we have to add these annotations back with quarkus-reasteasy-reactive
. I suspect the reactive extension is missing some bytecode enhancement. I'll investigate that later (or talk with the resteasy-reactive team).
Blocked by quarkusio/quarkus#16577: the
x-rh-identity
header is not sent because of a Quarkus bug, which leads to a failed RBAC call.It should be fixed in Quarkus
1.13.3.Final
.