geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-1430) Create TimedConfigStore (config store that timestamps deployments)
Date Thu, 13 Apr 2006 02:43:59 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1430?page=all ]
     
Dain Sundstrom closed GERONIMO-1430:
------------------------------------

    Fix Version: 1.1
                     (was: 1.2)
     Resolution: Fixed

All configurations now contain created timestamp.  This info is also contained in the ConfigurationInfo
object.

> Create TimedConfigStore (config store that timestamps deployments)
> ------------------------------------------------------------------
>
>          Key: GERONIMO-1430
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1430
>      Project: Geronimo
>         Type: Improvement
>     Security: public(Regular issues) 
>   Components: core
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Dain Sundstrom
>      Fix For: 1.1

>
> It would be helpful for the hot deploy directory if it could ask the config store for
the last time a module was deployed/redeployed.  That would let it calculate during startup
whether a file was newer or not.  After discussing this, it seems like this is not necessarily
a requirement for all config stores, but would be easy enough to support in an optional extension
for the config store.
> This issue is to create an additional interface to hold the new method (something like,
"public long getLastDeploymentTime(URI configId)"), and implement it for the file-based config
store.

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