[jira] Closed: (GERONIMO-1813) When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory

["Matt Hogstrom (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/GERONIMO-1813?page=all ]

Matt Hogstrom closed GERONIMO-1813.
-----------------------------------

    Resolution: Fixed
      Assignee: Matt Hogstrom

Applied to trunk 
New Revision: 474972
Modified:
    geronimo/server/trunk/modules/geronimo-hot-deploy/src/main/java/org/apache/geronimo/deployment/hot/DirectoryHotDeployer.java

and branches/1.1

Sending        hot-deploy/project.xml
Sending        hot-deploy/src/java/org/apache/geronimo/deployment/hot/DirectoryHotDeployer.java
Transmitting file data ..
Committed revision 474983.

> When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-1813
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1813
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Hot Deploy Dir
>    Affects Versions: 1.1
>         Environment: Win2k , JDK 1.4.2
>            Reporter: Mansoor
>         Assigned To: Matt Hogstrom
>            Priority: Minor
>             Fix For: 1.1.x, 1.2
>
>         Attachments: hotdeploy_patch1_06042006.txt, hotdeploy_projectxml_06042006.txt
>
>
> Hi ,
> Problem :
>        When already an application module say (hello.war) is deployed (either by using manually or hot deploy procedure ) , And when some one try to hot deploy the same application with same or different name ( say hello.war | hello2.war | hello2 directory ) ,  the server throws an exception saying there exists already an application deployed , But doesn't delete the module ( hello.war | hello2.war |  hello2 directory)  from hot deploy directory .
> Thus the next time the server starts , it tries to deploy the same module once again. 
> Here i have a piece of code put into DirectoryHotDeployer.java  file , which can solve the above issue and also to some extend users can get clean picture.
> Basically it deletes the asset from deploy directory ,which got failed to hot deploy

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira