geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-2036) SingleFileHotDeployer doesn't undeploy app on force if directory has changed
Date Thu, 18 May 2006 03:08:05 GMT
SingleFileHotDeployer doesn't undeploy app on force if directory has changed
----------------------------------------------------------------------------

         Key: GERONIMO-2036
         URL: http://issues.apache.org/jira/browse/GERONIMO-2036
     Project: Geronimo
        Type: Bug
    Security: public (Regular issues) 
    Versions: 1.1    
 Environment: windows xp
    Reporter: Joe Bohn
 Assigned to: Joe Bohn 
     Fix For: 1.1


When using the SingleFileHotDeployer with force deployment the image cannot be copied to a
new directory structure or tolerate the directory being renamed.   If this is done and the
hot deployer attempts to redeploy the application the result will be a failure to deploy because
a configuration with the same ID already exists.

The right best way to fix this would be to associate relative paths with the configurations
rather than the resolved paths.   However, that fix is a bit complication for this point in
the 1.1 release.   Therefore, this fix which is local to just SingleFileHotDeploy will check
for an installed configuration with the same ID if we are about to force deploy an application
and we haven't found a matching configuration already using the resolved path.

-- 
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


Mime
View raw message