2016-04-20 150 views
4

编辑不能部署到JBoss EAP 6.4

好的春天启动的耳朵,所以它看起来像SpringBootServletInitializer未检测到,因为它是一个JAR内的EAR,不是战争。我所做的是制作一个新模块,并将其纳入我的WAR中。这包含一个带有services文件夹的META-INF目录。该服务文件夹包含一个文件(javax.servlet.ServletContainerInitializer),内容为org.springframework.web.SpringServletContainerInitializer。这则试图部署WAR,但失败与以下:

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018104: Deployment error processing SCI for jar: test-1.0.0-SNAPSHOT.jar 
     at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.loadSci(ServletContainerInitializerDeploymentProcessor.java:202) 
     ... 7 more 
Caused by: java.lang.ClassCastException: org.springframework.web.SpringServletContainerInitializer cannot be cast to javax.servlet.ServletContainerInitializer 
     at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.loadSci(ServletContainerInitializerDeploymentProcessor.java:194) 
     ... 7 more 

再次,它看起来像在Servlet API与另一个冲突的 - 但只是从我可以告诉类路径的一个(和我甚至根据本测试规定的范围)。

原始

目前我在JBoss中6.4 EAP部署Spring的引导(1.3.2.RELEASE)EAR的几个问题。 EAR文件只是将一个瘦的WAR和所有的JAR包装在一个/ lib文件夹中。

我以前做过部署WAR文件所需的更改,但不幸的是我们遇到了部署必须是EAR的要求。

部署为WAR

要部署的应用程序作为一个WAR,我改变了以下内容:

的pom.xml

<!-- JavaEE 7 for JPA 2.1 --> 
    <dependency> 
     <groupId>javax</groupId> 
     <artifactId>javaee-api</artifactId> 
     <version>7.0</version> 
    </dependency> 

    <!-- Exclude Tomcat --> 
    <dependency> 
     <groupId>org.springframework.boot</groupId> 
     <artifactId>spring-boot-starter-web</artifactId> 
     <exclusions> 
      <exclusion> 
       <groupId>org.springframework.boot</groupId> 
       <artifactId>spring-boot-starter-tomcat</artifactId> 
      </exclusion> 
     </exclusions> 
    </dependency> 

    <!-- Include Servlet 3 --> 
    <dependency> 
     <groupId>javax.servlet</groupId> 
     <artifactId>javax.servlet-api</artifactId> 
     <version>3.0.1</version> 
    </dependency> 

JBoss的部署结构。 xml

<?xml version="1.0"?> 
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> 
    <deployment> 
     <exclude-subsystems> 
      <subsystem name="jpa"/> 
     </exclude-subsystems> 
     <exclusions> 
      <module name="javaee.api"/> 
     </exclusions> 
    </deployment> 
</jboss-deployment-structure> 

Application.java

@SpringBootApplication 
public class Application extends SpringBootServletInitializer { 

    private static final Class<Application> APPLICATION_CLASS = Application.class; 

    public static void main(String[] args) { 
     SpringApplication.run(APPLICATION_CLASS, args); 
    } 

    @Override 
    protected SpringApplicationBuilder configure(SpringApplicationBuilder application) { 
     return application.sources(APPLICATION_CLASS); 
    } 

} 

这些变化工作得很好,我现在可以部署WAR到JBoss 6.4。

部署为EAR

这是麻烦的开始。我创建了一个新的模块使用maven的入耳式插件来构建EAR文件:

<build> 
    <finalName>my-application</finalName> 
    <plugins> 
     <plugin> 
      <artifactId>maven-ear-plugin</artifactId> 
      <version>2.10.1</version> 
      <configuration> 
       <version>6</version> 
       <skinnyWars>true</skinnyWars> 
       <defaultLibBundleDir>lib</defaultLibBundleDir> 
       <fileNameMapping>no-version</fileNameMapping> 
       <modules> 
        <webModule> 
         <groupId>com.test.app</groupId> 
         <artifactId>my-application</artifactId> 
         <bundleFileName>my-application.war</bundleFileName> 
         <context-root>/my-app</context-root> 
        </webModule> 
       </modules> 
      </configuration> 
     </plugin> 
    </plugins> 
</build> 

我还添加了jboss-deployment-structure.xml下/ src目录/主/应用/ META-INF,这样它会被列入EAR(它需要处于最高级别)。试图部署这个结果的“成功”,但JBoss从来没有尝试在EAR内部署WAR。似乎需要一个web.xml。

所以在看文档,看来我需要定义一个web.xml像如下:

<?xml version="1.0" encoding="UTF-8"?> 
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> 

    <context-param> 
     <param-name>contextConfigLocation</param-name> 
     <param-value>com.test.app.Application</param-value> 
    </context-param> 

    <servlet> 
     <servlet-name>appServlet</servlet-name> 
     <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> 
     <init-param> 
      <param-name>contextAttribute</param-name> 
      <param-value>org.springframework.web.context.WebApplicationContext.ROOT</param-value> 
     </init-param> 
     <load-on-startup>1</load-on-startup> 
    </servlet> 

    <servlet-mapping> 
     <servlet-name>appServlet</servlet-name> 
     <url-pattern>/</url-pattern> 
    </servlet-mapping> 

</web-app> 

现在有一些额外的配置,如果我要下降到Servlet 2.5的 - 但我不”不想这样做。

尝试部署这将导致以下异常:

10:29:40,586 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/company-api-entity]] (ServerService Thread Pool -- 56) JBWEB000289: Servlet appServlet threw load() exception: java.lang.ClassCastException: org.springframework.web.servlet.DispatcherServlet cannot be cast to javax.servlet.Servlet 
      at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1154) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] 
      at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] 
      at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3593) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] 
      at org.apache.catalina.core.StandardContext.start(StandardContext.java:3802) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1] 
      at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] 
      at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] 
      at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] 
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_45] 
      at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_45] 
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] 
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] 
      at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] 
      at org.jboss.threads.JBossThread.run(JBossThread.java:122) 

这似乎有被加载在servlet的版本不匹配,但我似乎无法验证它(或排除)。我试过设置的范围,以提供(这样的JBoss版本接管),但这会导致以下错误:

11:18:47,141 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/company-api-entity]] (ServerService Thread Pool -- 52) JBWEB000289: Servlet appServlet threw load() exception: java.util.MissingResourceException: Can't find bundle for base name javax.servlet.LocalStrings, locale en_IE 
     at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1564) [rt.jar:1.8.0_45] 
     at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1387) [rt.jar:1.8.0_45] 
     at java.util.ResourceBundle.getBundle(ResourceBundle.java:773) [rt.jar:1.8.0_45] 
     at javax.servlet.GenericServlet.<clinit>(GenericServlet.java:95) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2] 

显然它使用JBoss 3.0 Servlet规范,但它似乎实际的servlet 3.0 JAR缺失。

有什么,我失踪? WAR实际上需要一个web.xml还是有其他方法?我正在尝试什么?

任何帮助将不胜感激。

回答

1

修复了这个问题。从WAR部署开始,我制作了一个额外的EAR模块。我不应该使用skinnyWar,而是将所有JAR都留在WAR中。这允许Spring正确引导Spring Boot servlet。

这具有以下配置:

<build> 
    <finalName>my-application</finalName> 
    <plugins> 
     <plugin> 
      <artifactId>maven-ear-plugin</artifactId> 
      <version>2.10.1</version> 
      <configuration> 
       <modules> 
        <webModule> 
         <groupId>com.test.app</groupId> 
         <artifactId>my-application</artifactId> 
         <bundleFileName>my-application.war</bundleFileName> 
         <context-root>/my-app</context-root> 
        </webModule> 
       </modules> 
      </configuration> 
     </plugin> 
    </plugins> 
</build> 

我还相信,有我的父母模块(根PO​​M)中没有编译范围的依赖性。

我那么做一定有在我耳边以下文件:

src/main/application/META-INF/jboss-deployment-structure.xml

虽然这是我的战争,我的主要问题是,我还是用的<deployment>代替<sub-deployment>

<?xml version="1.0"?> 
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> 
    <sub-deployment name="my-application.war"> 
     <exclude-subsystems> 
      <subsystem name="jpa"/> 
     </exclude-subsystems> 
     <exclusions> 
      <module name="javaee.api"/> 
     </exclusions> 
    </sub-deployment> 
</jboss-deployment-structure> 

这适当地排除了javaee.api模块和jpa子系统。

在此之后,EAR正确部署到JBoss。

相关问题