Is there any way to make @Context work happily with @Suspended?

[Yaytay]

Hi,

I'm using RestEasy with Vert.x.
I have a ContextInjector (https://github.com/Yaytay/vertx-resteasy-helpers/blob/main/src/main/java/uk/co/spudsoft/vertx/rest/RoutingContextInjector.java) that works just fine if the request has never been paused, but if the request gets paused the proxy loses the context (my guess is that there are ThreadLocals somewhere, but I don't know this for sure).

Is it possible to write a ContextInjector that works regardless of thread?

Thanks.

[0xShubhamSolanki]

Hey, yeah – RESTEasy classic + Vert.x is painful with @context once you hit @suspended / async. Classic relies way too much on ThreadLocals, so when the request gets paused and resumed (often on a different event-loop thread), the context disappears.
Quick ways that actually work:

1. Best move → switch to RESTEasy Reactive (or Quarkus REST if you're in that world). It’s made for Vert.x, no ThreadLocal nonsense, @context just works even after suspend/resume.

If you’re stuck on classic:

Don’t inject @context stuff (headers, UriInfo, etc.) directly inside the async method.
Grab everything you need early (in a filter or at the start of the method), stash it in Vert.x local context (ctx.putLocal("my:headers", headers)), then read it back later.

Or only inject safe things like Application, Providers, Configuration that don’t break on thread change.

Most people either go reactive or just capture stuff upfront. If you tell me exactly which @context types are failing, I can give a more pinpoint fix.