JBoss AS 7.1.1 jboss-deployment-structure.xml

时间:2022-11-01 00:03:00

I'm using JBoss AS 7.1.1 and I'm having trouble getting my EJB 3.0 server project to run. I get the error

我正在使用JBoss AS 7.1.1而我无法运行EJB 3.0服务器项目。我收到了错误

JBAS014777: Services which failed to start: service jboss.deployment.unit."GrahamsProj.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."GrahamsProj.ear".STRUCTURE: Failed to process phase STRUCTURE of deployment "GrahamsProj.ear"

JBAS014777:无法启动的服务:服务jboss.deployment.unit。“GrahamsProj.ear”.STRUCTURE:服务jboss.deployment.unit中的org.jboss.msc.service.StartException。“GrahamsProj.ear”.STRUCTURE:失败流程阶段部署的结构“GrahamsProj.ear”

I looked it up and the error seems to be something pertaining to my jboss-deployment-structure.xml. Here is what mine looks like:

我查了一下,错误似乎与我的jboss-deployment-structure.xml有关。这是我的样子:

<jboss-deployment-structure> 
    <deployment> 
        <dependencies> 
            <module name="org.slf4j" /> 
        </dependencies>
    </deployment>
</jboss-deployment-structure>

I don't know if I have any dependencies as I got the above from an example online. All I know is that the error means it doesn't like my jboss-deployment-structure.xml file. What can I do to get the file structured right?

我不知道我是否有任何依赖,因为我从网上的例子中得到了上述内容。我只知道错误意味着它不喜欢我的jboss-deployment-structure.xml文件。我该怎么做才能使文件结构正确?

1 个解决方案

#1


1  

I'd delete it.

我会删除它。

I am not an AS7 expert (is anyone, yet?), but i believe you only need it if you have particularly subtle deployment requirements. For straightforward module dependencies, you can put a Dependencies entry in your manifest instead.

我不是AS7专家(有人,但是?),但我相信如果你有特别微妙的部署要求,你只需要它。对于简单的模块依赖项,您可以在清单中放置一个Dependencies条目。

However, since SLF4J is one of the standard implicit dependencies, you don't even need to do that. You can just go ahead and use it, like you would a JDK or Java EE API.

但是,由于SLF4J是标准的隐式依赖项之一,因此您甚至不需要这样做。您可以继续使用它,就像使用JDK或Java EE API一样。

#1


1  

I'd delete it.

我会删除它。

I am not an AS7 expert (is anyone, yet?), but i believe you only need it if you have particularly subtle deployment requirements. For straightforward module dependencies, you can put a Dependencies entry in your manifest instead.

我不是AS7专家(有人,但是?),但我相信如果你有特别微妙的部署要求,你只需要它。对于简单的模块依赖项,您可以在清单中放置一个Dependencies条目。

However, since SLF4J is one of the standard implicit dependencies, you don't even need to do that. You can just go ahead and use it, like you would a JDK or Java EE API.

但是,由于SLF4J是标准的隐式依赖项之一,因此您甚至不需要这样做。您可以继续使用它,就像使用JDK或Java EE API一样。