Go to maven Combat (iv)---Multi-module Project---JBOSS Deployment issues

Original from: http://blog.csdn.net/liutengteng130/article/details/41622681 thanks!

These days in the framework of the only JBOSS encountered a lot of problems, these problems we are in the solution.

The original version of JBoss is 5.0 , and now JBoss has upgraded to the 7.3 version, which is a big leap. From the speed of the start is undoubtedly more and more fast, from the directory structure is very different from the mechanism of the operation is also very dissimilar.

JBOSS as 5: Second generation service-based architecture, component updates, support for distributed things and comprehensive Web service stacks, and more.

Features of JBOSS 7: Lightweight, Modular core , support for hot deployment, incremental deployment, elegant management, cluster domain management, firstClass components.

In terms of characteristics alone, These characteristics of JBOSS7 are the effects we want to achieve.

These days there are a lot of problems in deploying the project, because JBOSS7 has a modular core, so every time we deploy a variety of throw Jar package, otherwise it will be error:

Error [Org.jboss.as.server] (deploymentscanner-threads-1) JBAS015870: Deployment of Deployment "Gx_core.jar" is rolled back with the following error message:
{
"JBAS014671: Failed Service" = "jboss.deployment.unit.\" Gx_core.jar\ ". INSTALL "=" org.jboss.msc.service.StartException in service jboss.deployment.unit.\ "Gx_core.jar\". install:jbas018733: Processing INSTALL deployment \ "Gx_core.jar\" Phase failed
Caused by:org.jboss.as.server.deployment.DeploymentUnitProcessingException:JBAS011047: Components The Base.eao.impl.BaseEaoImpl component Class Studentimpl has an error:
JBAS011440: Unable to find a persistence unit named deployment \ "Gx_core.jar\" in Jc.entity,
"JBAS014771: Services with Lost/unavailable dependencies" = [
"Jboss.naming.context.java.comp.gx_core.gx_core. Studentimpl.validatorfactory missing [Jboss.naming.context.java.comp.gx_core.gx_core. Studentimpl] ",
"Jboss.naming.context.java.comp.gx_core.gx_core.common_EaoBean.ValidatorFactory Missing [ Jboss.naming.context.java.comp.gx_core.gx_core.common_EaoBean] ",
"Jboss.naming.context.java.comp.gx_core.gx_core. Studentimpl.validator missing [Jboss.naming.context.java.comp.gx_core.gx_core. Studentimpl] ",
"Jboss.naming.context.java.comp.gx_core.gx_core.common_EaoBean.Validator Missing [jboss.naming.context.java.comp.gx_ Core.gx_core.common_EaoBean] "
]
}

Let's start by introducing JBOSS directory structure:

Modules: Because JBoss 7 is a modular server, the module for the application server corresponds to a subdirectory here

The standalone directory contains configuration files for standalone mode, deployment content, writable regions, and so on.

Since JBOSS7 is a modular server, we are prompted to not find a dependency when we deploy the Jar package to the deployments. So we need to add the corresponding Jar subdirectory to the module:

Deployment directory with deployments:

This will not be a problem until the deployment is complete. But this certainly does not work, the steps are too cumbersome, need to find a more simple and convenient way to solve the problem. The JBOSS version upgrade, based on these features, shows that there must be a good solution to these problems, but we haven't found them yet. I hope the great God gives some advice.

Go to maven Combat (iv)---Multi-module Project---JBOSS Deployment issues