Quarkus RESTEasy Reactive vs Classic: Decision Guide
Choose between RESTEasy Reactive and Classic in Quarkus. Covers event-loop risks, @Blocking, dependency setup, and thread verification.
Loading…
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Choose between RESTEasy Reactive and Classic in Quarkus. Covers event-loop risks, @Blocking, dependency setup, and thread verification.
Goal: Ensure that request‑scoped data such as the current security principal or MDC context is available inside a Hibernate Panache repository method when it is invoked from a reactive RESTEasy resource that returns a Uni or Multi. Current behavior: Quarkus automatically off‑loads the blocking Panache call to a worker thread, but it does not propagate @Reque