[
http://issues.apache.org/jira/browse/GERONIMO-1813?page=comments#action_12414977
]
Aaron Mulder commented on GERONIMO-1813:
----------------------------------------
This patch is OK, but I think there's a better way to handle it.
I think when we detect a new or updated file, we should calculate its module ID
and see whether it's current'y deployed or not. If it is deployed, we should
redeploy, and if not, deploy. That would help with both this case (bad
deployment) and also if you deploy with the CLI and then copy a newer version
into the hot deploy directory.
Thanks,
Aaron
> 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
> Type: Bug
> Security: public(Regular issues)
> Components: Hot Deploy Dir
> Versions: 1.1
> Environment: Win2k , JDK 1.4.2
> Reporter: Mansoor
> Priority: Minor
> Attachments: hotdeploy_patch1_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
