Title: Undeploy an Application to a Standalone Server Instance with the Deployment Scanner
Describe the issue:
The steps of Procedure 10.8-B "Undeploy by removing the application" are not valid for the exploded WAR deployment. For this type of the deployment, the marker file must be deleted manually as is described in 10.8-A step "Undeploy by deleting the marker file".
Suggestions for improvement:
Add the information that this way of undeployment is not valid for exploded WAR archive and the user should use the "Undeploy by deleting the marker file".
Server response for the exploded WAR removal:
09:51:22,008 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015006: The deployment scanner found that the content for exploded deployment Transactions.war has been deleted, but auto-deploy/undeploy for exploded deployments is not enabled and the Transactions.war.deployed marker file for this deployment has not been removed. As a result, the deployment is not being undeployed, but resources needed by the deployment may have been deleted and application errors may occur. Deleting the Transactions.war.deployed marker file to trigger undeploy is recommended.
Verified for revision 6.4.0-15.