3 Replies Latest reply on Sep 13, 2018 11:20 AM by ehugonnet

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

    Harshavardhan Bachina Newbie

      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?