Bug 899466 (JBPAPP6-638)
| Summary: | Undeployment operation using the Management Console of an application deployed by filesystem copy is not persisted | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Dominik Pospisil <dpospisi> | ||||||||
| Component: | Web Console | Assignee: | Heiko Braun <ike.braun> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 6.0.0 | CC: | brian.stansberry, dpospisi, ike.braun, ssilvert | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | EAP 6.0.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-638 | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-05-10 13:18:23 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Dominik Pospisil
2011-08-16 11:03:43 UTC
Steps to Reproduce: Removed: 1. Start EAP 6.0.0 Alpha in standalone configuration 2. deploy web application 3. undeploy the application using Admin console's Manage Deployments -> Remove command 4. restart the server Now the application is redeployed. Added: 1. Start EAP 6.0.0 Alpha in standalone configuration 2. deploy web application by copying app war file to EAP_HOME/standalone/deployments 3. undeploy the application using Admin console's Manage Deployments -> Remove command 4. restart the server Now the application is redeployed. Link: Added: This issue relates to JBQA-5289 Dominik, is there an upstream JIRA for this issue? Link: Added: This issue is related to AS7-3595 Link: Added: This issue is related to AS7-784 AS7-784 is the right upstream JIRA. Link: Added: This issue is duplicated by JBPAPP-7922 This is not a console problem. Once AS7-784 is resolved, this should work correctly in console and CLI. However, if you want me to hide filesystem deployments we can look into that. Reassigning to Brian for his comments. AS7-784 is not going to be resolved for EAP 6.0.0.GA, so disabling the ability to control their lifecycle in the console makes sense. I wouldn't advocate hiding them completely though. That seems like a cure that's worse than the disease. Thanks Brian. I'm taking this back. I'd like to get some opinions on it though. I could try just hiding the "Remove" and "Update Content" links for filesystem deployments. But that would look strange and the user wouldn't understand why those operations are not available. Ideally, I'd like a way to show the user that these are filesystem deployments and they must be controlled from the filesystem. Any thoughts on how best to communicate the situtation to the user? Attached file showing what deployment screen looks like currently. Attachment: Added: deployments.png Thanks for the screen shot! Perhaps replace the links in the columns with "N/A" and a little question mark icon? Or instead of the question mark add the "Need help?" thing above the box. For text, something like: "This deployment is managed by a file system deployment scanner. To disable or remove the deployment or update its content, update the directory containing the deployment." BTW, I don't see "Update content" ever being supported for scanner deployments. I don't think we want to start having to support uploading files to the server and then dropping them into the deployments/ dir. Theoretically we could -- unless the admin didn't give the server account write perms to the file, which may very well happen in some odd cases. Yea, supporting "Update Content" would be very problematic for filesystem deployments. I'm thinking of replacing the links with a file icon. I like your explanatory text. I'll use it as long as you promise not to sue for copyright infringement. :-) https://github.com/heiko-braun/as7-console/pull/104 After thinking this over for awhile, I think I came up with a really simple and obvious way to communicate with the user. I just put static text "Use File System" in place of the command link. I've attached a screen shot so you can see how this looks in context. Attachment: Added: UseFileSystem.png Based on the commit date, setting fix version to ER7 I am not seeing "Use File System" hints in ER7 build. The relevant fields are empty. Attaching screenshot of ER7 build with three apps deployed - deployment0 was deployed using console and the other two using filesystem copy. Attachment: Added: missing-use-fs.jpg Someone changed this so that it says "File System Deployment" under the name and it leaves the other columns blank. I assume Heiko made these changes. I'll assign to him and you guys can discuss what you want to do. For the record, I'm fine with either approach. You'd need to elaborate. A FS deployment can not be changed through the console anymore. And it shouldn't. My assumption was that it is missing by mistake. But I am fine with how it looks right now. Closing, reopen if anyone has some objections. Docs QE Status: Removed: NEW |