JBoss AS 7 禁用热部署 [英] JBoss AS 7 disable hot deployment

查看:20
本文介绍了JBoss AS 7 禁用热部署的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在以前的版本中,您只需禁用 conf/jboss-service.xml 中的 ScanEnabled 属性.

In previous versions you just disable the ScanEnabled attribute in conf/jboss-service.xml.

我想知道您如何在 JBoss 7 上禁用此功能

I am wondering how do you disable this on JBoss 7

谢谢

推荐答案

我今天为此苦苦挣扎.虽然您可以将 auto-deploy-zip 和 auto-deploy-exploded 都设置为 false,但这实际上并没有禁用热部署,它只是使您必须通过触摸 .dodeploy 文件来启动热部署来触发热部署.此外,这要求您为要在容器启动后启动的每个工件接触一个 .dodeploy 文件.

I was struggling with this today. While you can set auto-deploy-zip and auto-deploy-exploded both to false, this doesn't actually disable hot deploy, it just makes it so that you have to trigger hot deploy by touching a .dodeploy file to initiate it. Additionally, this requires that you touch a .dodeploy file for each artifact that you want to start after the container is started.

阅读:https://community.jboss.org/wiki/TurnDeploymentScannerDown和这个:https://docs.jboss.org/author/display/AS7/Deployment+Scanner+configuration 我意识到禁用热部署的正确方法是将扫描间隔设置为负数,这会导致部署扫描器仅在启动时运行.

Reading over: https://community.jboss.org/wiki/TurnDeploymentScannerDown and this: https://docs.jboss.org/author/display/AS7/Deployment+Scanner+configuration I realized that the proper way to disable hot deploy is to set the scan-interval to a negative number, this causes the deployment scanner to run on startup only.

这篇关于JBoss AS 7 禁用热部署的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆