You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rakesh Midha (JIRA)" <ji...@apache.org> on 2006/11/24 06:27:02 UTC
[jira] Commented: (GERONIMO-2025) Undeploy and redeploy with no
version leaves dangling entries in config.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2025?page=comments#action_12452361 ]
Rakesh Midha commented on GERONIMO-2025:
----------------------------------------
Added patch which removes leaves dangling entries in config.xml when newer version of module is deployed.
This is done by adding a method removeEarlierVersion in confiuration's ServerOverride.java. This method is used after new configuration is added.
> Undeploy and redeploy with no version leaves dangling entries in config.xml
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-2025
> URL: http://issues.apache.org/jira/browse/GERONIMO-2025
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, kernel
> Affects Versions: 1.1
> Reporter: Aaron Mulder
> Assigned To: Rakesh Midha
> Fix For: 1.2
>
> Attachments: removeunwantedconfig.patch
>
>
> If you deploy an application with no version and then undeploy it, we leave an entry for it (with a timestamp version number) in config.xml, just marked as load=false.
> If you later deploy the application again, you get a new timestamp version number and a new entry is written into config.xml. Do this (undeploy/deploy) a few times and config.xml gets kind of messy.
> It would be be good to delete entries from config.xml on undeploy if they have no actual settings.
> It would be good to detect that a previous version is in conifg.xml but not in the repository and delete the settings from config.xml if the artifact has no version number and a newer copy is deployed.
> This is not a huge priority since nothing breaks, it just makes config.xml kind of crufty.
--
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