Remotely Deploying exploded content using "deploy()" function is creating .deployed file in wildfly11.0.0 but not in wildfly9.0.1

[hvardhan20]

I am trying to deploy an exploded ear through jboss cli. The approach I am following is by executing the following commands one by one:

/deployment=test.ear:add(runtime-name="test.ear",content=[{"path"=>"$EAR_FULL_PATH","archive"=>false}])

The above command is making an insertion in standalone.xml like this

<deployments>

        <deployment name="test.ear" runtime-name="test.ear" enabled="false">

            <fs-exploded path="/opt/MyApp/wildfly11.0.0/server/Method_Server/deployments/test.ear"/>

        </deployment>

</deployments>

and then it's deploying the same using below command.

/deployment=test.ear:deploy()

The difference observed between wildfly 9.0.1 and 11.0.0 is that 11.0.0 creates .deployed marker file in deployments folder after executing deploy() function unlike 9.0.1.

Could you please let me know if this an expected behaviour or a bug in either 11 or 9?

[ehugonnet]

Yes this is an expected behaviour as now archived deployments deployed through the scanner are also managed.

Please look at [WFCORE-27] Deployment scanner treats zipped content as unmanaged - JBoss Issue Tracker

[hvardhan20]

Thank you ehugonnet for the quick response.

The test.ear which I am trying to deploy is actually exploded content. It is not an archive. Just the name of the folder is test.ear. The actual ear content is extracted into this folder which I am deploying using the "add()" and "deploy()" functions. Notice "archive"=>false in the add() function.

Since this is treated as managed in wildfly11, it is creating a marker file. The problem that I am facing is when I try to restart wildfly. I see the below error because of the entry in the standalone.xml and also the marker file. Hence I am unable to start wildfly once I stop it.

Operation ("add") failed - address: ([("deployment" => "test.ear")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"test.ear\")]"

I have to remove either one(standalone entry or marker file) to restart wildfly successfully which is not a viable solution for us since the deployment process is remotely done.

Is there any way I can circumvent this behavior of wildfly11 to not make it create a marker file like wildfly 9?

PS: I have tried --unmanaged flag while deploying. It is still creating the marker file.

Appreciate your help in this regard.

[ehugonnet]

Messing between scanner and console is wrong. If you want to use exploded deployments with the scanner then use the .dodeploy .doundeploy etc. files not the jboss console.

Also you can use exploded managed deployments without the scanner with JBoss Developper Studio or using the console but then you will have to add every local file manually using the add-content operation.