JBoss RESTEasy中@Context注入HttpServletRequest始终为空求助

Hey there, let's work through this frustrating null HttpServletRequest issue you're hitting. I've dealt with similar context injection problems in Resteasy, so here are some practical, actionable fixes to try:

1. Verify Undertow-Resteasy Integration Setup #

The most common culprit here is a misconfigured integration between Undertow and Resteasy. If the two aren't properly bound, request context data won't propagate:

• If you're using embedded Undertow, make sure you're using Resteasy's official UndertowJaxrsServer to deploy your JAX-RS application instead of rolling your own handler setup. Example:

  UndertowJaxrsServer server = new UndertowJaxrsServer();
  server.start();
  server.deploy(YourJaxrsApplication.class);
  

• If you're deploying as a WAR file, double-check your web.xml for the required Resteasy components:
  • The ResteasyBootstrap listener to initialize Resteasy's context
  • The HttpServletDispatcher servlet mapped to your API paths
    Missing either will break context injection.

2. Fix Your @Context Injection Pattern #

Your current code has a red flag: you're returning a LActionsService instance from a resource method, then manually calling injectProperties. Resteasy manages resource instances and their context injection automatically—manual interference can break this:

• Move the @Context injection directly into your LActionsService class instead of trying to pass it through the factory method:

  public class LActionsService {
      @Context
      private HttpServletRequest request;
  
      @POST
      @Path("perform-login")
      public Response handleLogin() {
          if (request != null) {
              // Use the request object here
          }
          // ... rest of your logic
      }
  }
  

• If you need to create LActionsService dynamically, let Resteasy handle instantiation via @Inject or by registering it as a singleton in your JAX-RS application class—don't manually new up instances.

3. Avoid Manual ResteasyProviderFactory Calls #

Calling ResteasyProviderFactory.getInstance() grabs the global factory instance, which doesn't have access to the current request's context. Instead:

• Rely on @Context injection directly into method parameters or class fields (as shown above)
• If you absolutely need to fetch context data programmatically, use the request-scoped provider factory:

  HttpServletRequest request = ResteasyProviderFactory.getContextData(HttpServletRequest.class);
  

  Note the static getContextData() method instead of grabbing the global instance.

4. Fallback: Fetch from Resteasy's HttpRequest #

If direct injection still fails, you can pull the servlet request from Resteasy's own request object:

import org.jboss.resteasy.spi.HttpRequest;

HttpRequest resteasyRequest = ResteasyProviderFactory.getContextData(HttpRequest.class);
if (resteasyRequest != null) {
    HttpServletRequest servletRequest = 
        (HttpServletRequest) resteasyRequest.getAttribute("javax.servlet.http.HttpServletRequest");
}

This bypasses some of the direct context injection layers and can work around configuration quirks.

5. Check for Context Propagation Disabling #

Resteasy 3.x enables context propagation by default, but custom configurations might accidentally disable it. Add this system property at startup to ensure it's enabled:

-Dresteasy.context.propagation=true

Hopefully one of these steps fixes your null request issue. If you're still stuck, share a bit more about your deployment setup (embedded vs WAR) and your JAX-RS application class code—those details can help narrow things down further.

内容的提问来源于stack exchange，提问作者tech_geek