0

How to configure WildFly 8.2.1 to:

  1. Not auto-deploy from "deployments" folder when server running
  2. Always deploy from "deployments" whent starting up, ignoring previous deploy result

If I set scan-enabled="false" for deployment-scanner, WildFly didnt deploy at startup even new files. When scan-enabled="true", WildFly didn't deploy files that failed to deploy at previous start up, but not changed.

Rustam
  • 1,397
  • 1
  • 13
  • 17

2 Answers2

1

To avoid auto deploy set auto-deploy-zipped="false" auto-deploy-exploded="false" for deployment-scanner in standalone.xml.

But whenever you want to deploy another file then you have to add MARKER FILES for it.

For example, the marker file to indicate the HelloWorld.war file should be deployed named HelloWorld.war.dodeploy in deployments folder and file should have content - HelloWorld.war.

Then only it will deploy your new file automatically.

Refer this and this link for some more info.

PVR
  • 885
  • 9
  • 18
  • If scan-enabled="false" then WildFly will ignore marker files at startup and at runtime – Rustam May 19 '16 at 11:41
  • I have following entry in my standalone.xml Which works fine with marker file at server startup in wildfly 8.2.1 – PVR May 19 '16 at 12:17
  • if attribute scan-enabled missed then scan-enabled=true – Rustam May 19 '16 at 13:13
  • Though its true, it will not auto deploy your new added files without adding MARKER file. – PVR May 19 '16 at 13:20
0

If scan-enabled="false" then WildFly will ignore marker files at startup and at runtime. Alsow WildFly will ignore all deployments in deploy folder, even if that deployments was successfully deployed before.

Left only 2 ways:

  1. Set scan-interval less than 1 (with scan-enabled="true"). It will enable only one scan at startup. After that WildFly also will ignore any changes in deploy folder
  2. Deploy through admin console
Rustam
  • 1,397
  • 1
  • 13
  • 17