Kedar has described one way of undeploying an auto-deployed app.
There is another way. Because copying the archive file to the
auto-deploy directory is how you triggered the auto-deployment in the
first place, GlassFish also allows you to auto-undeploy the application
by deleting the file from the auto-deploy directory. It's a consistent
technique in that it uses the file system operations for both deployment
and undeployment. It also helps to keep the auto-deploy directory
clean. Although that's not really a concern from GlassFish's point of
view it might be from yours.
As has already been mentioned recently, there is no way to auto-deploy
or auto-undeploy an application using the admin console. You can, as
Kedar mentions, use the admin console to undeploy a previously
auto-deployed application but that does not remove the file from the
auto-deploy directory. You can do so manually after undeploying the
application using the console (or the command line) without problems.
The documentation does explain this, although it is buried pretty
deeply. In the Application Deployment Guide at
https://glassfish.dev.java.net/nonav/javaee5/docs/AS91ADG.pdf look in
the "Deployment for Development" section on "Automatic Deployment"
starting on page 35.
- Tim
glassfish_at_javadesktop.org wrote:
> Sorry it could not be evident.
>
> - admin-console: Server->Applications->Web Apps -> Find the app and undeploy
> - CLI: asadmin undeploy <application-name>
>
> The name of the application that is auto-deployed is the name of the war file, i.e. "foo" if you
> auto-deployed "foo.war".
>
> Regards,
> Kedar
> [Message sent by forum member 'km' (km)]
>
> http://forums.java.net/jive/thread.jspa?messageID=242275
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>