2

In JBoss 6 AS, the hot deployment location is ${JBOSS_HOME}/server/default/deploy where I can unpack WAR or EAR and change content of any configuration file and it works without restart.

Similarly, in Wildfly 8 AS, can anyone help me to know about the hot deployment location. I tried unpacking WAR in ${WILDFLY_HOME}/standalone/deployments folder but it is not picking up the unpacked WAR folder. It considers file only with .war extension. Can anyone help me on the same. Many thanks.

Also, if there is a good guide on usage of wildfly-maven-plufgin, please share m Can anyone help me on the same. Many thanks.

sridhar
  • 1,117
  • 5
  • 31
  • 59
  • You followed all the steps in the documentation? https://docs.jboss.org/author/display/WFLY8/Application+deployment – Gimby Apr 21 '15 at 12:21

1 Answers1

5

The full documentation is found here:

https://docs.jboss.org/author/display/WFLY8/Deployment%20Scanner%20configuration.html

What you need to do to enable automatic deployment of exploded (unpacked) archives is to set the auto-deploy-exploded to true in your standalone.xml configuration file:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0">
    <deployment-scanner 
        scan-interval="5000"
        relative-to="jboss.server.base.dir" 
        path="deployments"
        auto-deploy-exploded="true" />
</subsystem>

This would scan the deployments directory every 5 seconds for exploded archives.

As stated in the documentation, without the auto-deploy-exploded property, you would need to manually create a .dodeploy file:

Controls whether exploded deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content.

Magnilex
  • 11,584
  • 9
  • 62
  • 84