通过cargo-maven2-plugin在JBoss中部署的战争无法通过JBoss AS管理控制台访问
我正在使用以下 POM 配置将战争部署到远程 JBoss 5.1.0
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.0.2</version>
<configuration>
<container>
<containerId>jboss51x</containerId>
<type>remote</type>
</container>
<configuration>
<type>runtime</type>
<properties>
<cargo.hostname>localhost</cargo.hostname>
<cargo.remote.username>****</cargo.remote.username>
<cargo.remote.password>****</cargo.remote.password>
</properties>
</configuration>
<deployer>
<type>remote</type>
<deployables>
<deployable>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<type>war</type>
<properties>
<context>/${project.artifactId}</context>
</properties>
</deployable>
</deployables>
</deployer>
</configuration>
<executions>
<execution>
<id>start-container</id>
<phase>pre-integration-test</phase>
<goals>
<goal>deployer-deploy</goal>
</goals>
</execution>
<execution>
<id>stop-container</id>
<phase>post-integration-test</phase>
<goals>
<goal>deployer-undeploy</goal>
</goals>
</execution>
<execution>
<id>verify-deploy</id>
<phase>install</phase>
<goals>
<goal>deployer-deploy</goal>
</goals>
</execution>
<execution>
<id>clean-undeploy</id>
<phase>pre-clean</phase>
<goals>
<goal>deployer-undeploy</goal>
</goals>
</execution>
</executions>
</plugin>
它工作正常,并且 Web 项目通过 http://localhost:8080/my-web-project/
但是在 JBoss AS 管理控制台中没有任何痕迹(http://localhost:8080/admin-console/)
正常吗?
提前致谢
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
长期以来,JBoss AS 上使用 Cargo 的远程部署仅得到部分支持,这也许可以解释问题。此问题已记录在
CARGO-416中,已修复在货物 1.0.3 中。因此,从 Cargo 1.0.3 开始,JBoss 上的远程部署现在应该得到完全支持,并记录在专用的 JBoss 远程部署器 wiki 页面。尝试一下。
Remote deployment on JBoss AS with Cargo has been only partially supported during a long time, and this might explain the problem. This was logged in
CARGO-416which has been fixed in Cargo 1.0.3.So, as of Cargo 1.0.3, remote deployment on JBoss should be now fully supported and is documented in the dedicated JBoss Remote Deployer wiki page. Give it a try.