An issue present in previous releases of JBoss EAP 6 that caused the upload of files through the Manage Deployments screen to complete, even if the upload was canceled by the user, has been corrected in this release.
The issue presented because older versions of the product allowed users to cancel a file upload operation after the file copy had occurred but before the deployment entry had been added to *domain.xml*.
In this release of the product, the console workflow has been redesigned to remove the cancel option during the operation, preventing incomplete operations and inconsistent states between saved files and <deployment> entries in *domain.xml*.
Description of problem:
In the Manage Deployments screen, after to cancel the step 2 to add a deployment file, the file is uploaded and added to data dir, but the deployment is not added to the domain.xml file (in the <deployments> tag)
Version-Release number of selected component (if applicable):
JBoss EAP 6.1.1
Steps to Reproduce:
1. Go to management console
2. Runtime > Manage Deployments > Add
3. Browse > select a deployment file > Next > Cancel.
The content is added to data:
INFO [org.jboss.as.repository] (HttpManagementService-threads - 9) JBAS014900: Content added at location /opt/JBoss/domain/data/content/xx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/content
But there is not a reference to this deployment file in the domain.xml.
Therefore, it is not possible to remove this deployment file using the management console or CLI.
If the upload is canceled, the deployment file does not have to be added to the data directory.
Modified Doc Text content and marked for inclusion in the 6.2 Release Notes document.
Currently there's no way to remove canceled deployments using a management operation (please comment if I'm wrong). Lower the priority as this does not affect the deployment feature as such.
As part of an overall bugzilla cleanup, I'm going to reassign this to 'Domain Management'. In order to fix this as part of the console, we need a related management operation to get rid of canceled deployments. However IMO this has low priority, so we might as well close this.
Harald Pehl <email@example.com> updated the status of jira HAL-342 to Closed
I agree with Brian that the workflow can be optimized. And yes this is something we can do for EAP 6.4.
By changing the wizard to a "one-step" dialog, we can defer the upload. For the user both the upload and actual deployment would happen as one atomic operation. Thus the particular issue with left-over deployment artifacts on the server should be fixed.
I'm reassigning this to "Web Console" and set the target to EAP 6.4
Harald Pehl <firstname.lastname@example.org> updated the status of jira HAL-342 to Reopened
Harald Pehl <email@example.com> updated the status of jira HAL-342 to Coding In Progress
Harald Pehl <firstname.lastname@example.org> updated the status of jira HAL-342 to Open
Harald Pehl <email@example.com> updated the status of jira HAL-342 to Resolved
Should this still remain in POST state?