2014-12-19 57 views
1

在我的previous question(谢谢@Andy Wilkinson)中,我发现所有到undertowEmbeddedServletContainer的传入请求都由工作线程(阻塞操作)处理。Spring Boot Undertow在同一应用程序中添加阻塞处理程序和NIO处理程序

根据Andy的说法,我尝试添加一个UndertowBuilderCustomizer以覆盖ServletInitializerHandler以使用非阻塞处理程序处理传入请求。

@Bean 
public UndertowEmbeddedServletContainerFactory undertowEmbeddedServletContainerFactory(){ 
    UndertowEmbeddedServletContainerFactory undertowEmbeddedServletContainerFactory = new UndertowEmbeddedServletContainerFactory(); 
    undertowEmbeddedServletContainerFactory.addBuilderCustomizers(new UndertowBuilderCustomizer() { 

     @Override 
     public void customize(Undertow.Builder builder) { 
      builder.setHandler(new HttpHandler() { 
       @Override 
       public void handleRequest(HttpServerExchange exchange) throws Exception { 
        exchange.getResponseSender().send("test"); 
       } 
      }); 
     } 
    }); 
    return undertowEmbeddedServletContainerFactory; 
} 

在这种定制我设定的建设者rootHandler的NIO处理程序。 但它是由UndertowEmbeddedServletContainer在启动阶段重写了ServletInitializerHandler

private Undertow createUndertowServer() { 
    try { 
     HttpHandler servletHandler = this.manager.start(); 
     this.builder.setHandler(getContextHandler(servletHandler)); 
     return this.builder.build(); 
    } 
    catch (ServletException ex) { 
     throw new EmbeddedServletContainerException(
       "Unable to start embdedded Undertow", ex); 
    } 
} 

由于这个问题的标题说:我想有阻塞和非阻塞处理,其中阻塞处理程序通过@Controller管理注释,以及Spring处理NIO处理程序的位置。

我找到了一个解决方案,但作为初学者,我不知道它是否是一个好的解决方案。

HandlerPath注释

@Retention(RetentionPolicy.RUNTIME) 
@Documented 
@Target({ElementType.TYPE}) 
public @interface HandlerPath { 

    public String path() default ""; 

} 

创建豆实现的HttpHandler

@Component 
@HandlerPath(path = "/hello-nio") 
public class HelloHandler implements HttpHandler{ 

    @Autowired 
    HelloService helloService; 

    @Override 
    public void handleRequest(HttpServerExchange exchange) throws Exception { 
     exchange.getResponseSender().send(helloService.sayHello("Josselin")); 
    } 
} 

创建一个简单的控制器

@Controller 
public class HelloController { 

    @RequestMapping("/hello") 
    @ResponseBody 
    public String sayHello(){ 
     return "hello"; 
    } 
} 

创建类实施ServletExtension

public class NonBlockingHandlerExtension implements ServletExtension{ 

    @Override 
    public void handleDeployment(DeploymentInfo deploymentInfo, final ServletContext servletContext) { 
     deploymentInfo.addInitialHandlerChainWrapper(new HandlerWrapper() { 
      @Override 
      public HttpHandler wrap(final HttpHandler handler) { 

       WebApplicationContext ctx = WebApplicationContextUtils.getWebApplicationContext(servletContext); 
       Map<String, Object> handlers = ctx.getBeansWithAnnotation(HandlerPath.class); 

       PathHandler rootHandler = new PathHandler(); 
       rootHandler.addPrefixPath("/", handler); 
       for(Map.Entry<String, Object> handlerEntry : handlers.entrySet()){ 
        if(handlerEntry.getValue() instanceof HttpHandler){ 
         HttpHandler httpHandler = (HttpHandler) handlerEntry.getValue(); 
         String path = httpHandler.getClass().getAnnotation(HandlerPath.class).path(); 
         rootHandler.addPrefixPath(path, httpHandler); 
        } 
       } 
       return rootHandler; 
      } 
     }); 
    } 
} 

在该方法中,默认ServletInitializer处理程序绑定到“/”上下文,并且管理由弹簧,因此,所有阻止请求可以通过@Controller(多个)进行处理。 然后,我尝试发现所有注释为@HandlerPath的豆,然后根据@HandlerPath.path属性向rootHandler添加新的prefixPath

最后

创建一个目录META-INF.services

创建一个文件io.undertow.servlet.ServletExtension,并添加一行:

org.me.undertow.NonBlockingHandlerExtension 

结果

所有工作都像一个魅力,NIO处理程序被称为bi时找到URL,所以阻止处理程序。

任何人都可以请让我知道,如果这种解决方案可以改善任何方式? 此外,由于NIO处理程序的URL不是由Spring管理的,我想我必须使用globaleMethodSecurity并设置来保护NIO处理程序?

回答

0

最近我有类似的问题,我发现UndertowEmbeddedServletContainerFactory规定addDeploymentInfoCustomizers()可以用来把自定义HttpHandler在处理程序链的开始。

@Bean 
public UndertowEmbeddedServletContainerFactory embeddedServletContainerFactory(RootHandler rootHandler) { 
    UndertowEmbeddedServletContainerFactory factory = new UndertowEmbeddedServletContainerFactory(); 

    factory.addDeploymentInfoCustomizers(deploymentInfo -> 
      deploymentInfo.addInitialHandlerChainWrapper(rootHandler::setNext)); 

    return factory; 
} 

样品RootHandler

@Component 
public class RootHandler implements HttpHandler { 

    private HttpHandler next; 

    @Autowired 
    public RootHandler(...) { 
    } 

    @Override 
    public void handleRequest(HttpServerExchange exchange) throws Exception { 
     if (exchange.getRelativePath().startsWith("/service")) { 
      handleServiceRequest(exchange); 
     } else { 
      next.handleRequest(exchange); 
     } 
    } 

    private void handleServiceRequest(HttpServerExchange exchange) { 

     // ... 

     exchange.getResponseSender().send("OK"); 
    } 

    public HttpHandler setNext(HttpHandler next) { 
     this.next = next; 
     return this; 
    } 
}