[GLASSFISH-20542] Allow Manually Deleting Application Deployments Created: 16/May/13  Updated: 16/May/13

Status: Open
Project: glassfish
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: reza_rahman Assignee: michael.y.chen
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Received the following feedback from active Java EE community member Henk (https://twitter.com/henk53) that I think needs to be investigated further:

"...one complaint I occasionally hear is that you can't clean GlassFish' deployments by simply deleting stuff from some directory. You have to run it through asadmin, which might start up stuff before it cleans.

This is extra painful in Eclipse. The Oracle tooling starts up GlassFish when you do a server -> clean, but if the deployment is problematic you'll have to sit through a whole slew of error messages and delays first. Then there's no choice for whether that startup needed for cleaning is debug mode or normal mode (it's normal), so if you actually wanted debug you have to shut-down the server after cleaning and then starting it up again in debug.

Just deleting stuff from a directory would just be so much more easier and simpler. If Tomcat, Jetty and JBoss can do it, maybe GlassFish can do it to?"

Do let me know if anything needs to be explained further - I am happy to help.

Please note that these are purely my personal views and certainly not of Oracle's as a company.


Generated at Sat Apr 25 00:27:42 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.