Can you use request scoped @Context variables in a singleton ContextResolver in JAX-RS?

Question

I'm using Jersey 1.13 with Spring. I've got a ContextResolver defined like so:

@Provider
public class ThemeSourceContextResolver implements ContextResolver<ThemeSource> {

    @Context private HttpServletRequest request;

    @Override
    public ThemeSource getContext(Class<?> type) {
        return new DefaultThemeSource(request);
    }
}


<bean id="themeSourceContextResolver" scope="singleton" class="com.example.ThemeSourceContextResolver" />

Is the above valid? Specifically, is it "legal" (or does it make sense) to use the @Context private HttpServletRequest request in a ContextResolver? Since the ContextResolver is a singleton, does Jersey/JAX-RS do some threadlocal proxy magic or something to allow it to have access to the HttpServletRequest of every request?

score 0 · Answer 1 · answered Dec 07 '12 at 13:12

0

It's not valid. @Context is injected only into JAX-RS resources. ContextResolver<?> has nothing to do with request context, mostly because it's a singleton, as you said.

answered Dec 07 '12 at 13:12

yegor256

102,010
123
446
597

I've used `ContextResolver` in Jersey 1.19 to chain providers and pass values between them. It doesn't seem to work in 2.x though. – Martynas Jusevičius Apr 09 '20 at 20:27

score 0 · Answer 2 · answered Jan 30 '15 at 02:29

To update this answer for Jersey 2.14:

The answer is now "sometimes". Jersey does indeed do proxy magic for specific @Context variables, namely HttpHeaders, Request, UriInfo and SecurityContext. Your specific case, HttpServletRequest, is not supported.

See https://jersey.java.net/documentation/latest/jaxrs-resources.html#d0e2578.

Can you use request scoped @Context variables in a singleton ContextResolver in JAX-RS?

2 Answers2

Linked