geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-739) Review location of config-store directory
Date Mon, 21 Nov 2005 07:28:41 GMT
    [ ] 

David Jencks commented on GERONIMO-739:

My opinion is that this appears to be an issue only if you allow mutable configurations, which
I regard as a serious conceptual error.  Once configurations are immutable, the question reduces
to "who can add and remove configurations from the config store" .  This to me is a security
issue: if you can't control who is changing the config store you shouldn't be sharing the
repository either.

On another related note, I believe we will be able to have a config store that uses packed
configurations in the repository (or possibly unpacked configurations in the repository).
 Using such a config-store it really doesn't make sense to consider a "location" under var.

> Review location of config-store directory
> -----------------------------------------
>          Key: GERONIMO-739
>          URL:
>      Project: Geronimo
>         Type: Task
>   Components: core
>     Reporter: John Sisson
>      Fix For: 1.0

> Issue created as a result of dev list thread "Questions on Geronimo's var directory and
the config-store directory"
> Currently Geronimo has a var directory that is intended for holding data specific to
a particular Geronimo instance and not intended to be shared by multiple instances of geronimo.
> The config-store directory is not currently stored under the var directory.
> It has been suggested that this should be reviewed.  Also more thought is required as
to how the config-store will be used when Geronimo is eventually clustered.  How will deployment
and loading of configurations work on the instances in the cluster?  This may impact the decision
on where the config-store is placed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message