Grails 3在JBoss EAP 6.2.0中的战争不起作用 [英] grails 3 war in JBoss EAP 6.2.0 does not work

问题描述

当我尝试在JBoss EAP 6.2.0.GA(AS 7.3.0.Final-redhat-14)中运行一个非常简单的grails 3(3.0.7)应用程序作为战争(已移除嵌入式tomcat)时，所有请求都结束了在HTTP 404中 同样的战争在Tomcat中也有效.

When I try to run a very simple grails 3 (3.0.7) application as war (with embedded tomcat removed) in JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) all requests end up in a HTTP 404. The same war works in Tomcat.

在网上搜索后，我发现与Spring Boot相关的以下内容:

Searching the web I found the following related to Spring Boot:

在Jboss EAP上的springBoot应用程序，未使用servlet上下文

不幸的是，在 application.yml (以yml格式)中配置属性 server.servlet-path 无效.

Unfortunately configuring the property server.servlet-path in application.yml (in yml format) did not work.

推荐答案

查看grails 3来源:

Looking into the grails 3 source:

我找到了解决方案. 在 application.yml 中添加以下配置:

I found the solution. In application.yml add the following configuration:

grails:
    web:
        servlet:
            path: /*

从 web:开始到现有的 grails:部分. 然后，所有请求都将按预期方式工作.

starting with web: into the existing grails: section. Then all requests are working as again as expected.

这篇关于Grails 3在JBoss EAP 6.2.0中的战争不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！