On Friday 23 February 2007 11:23, David Leangen wrote:
> I want to have default properties for a bundle sitting in a
> properties file that is committed to the svn repository (as is done
> presently).
>
> In addition, I want each user/developer to have the possibility of
> using an optional properties file if they want to change any of the
> default values. Such optional properties file would only be saved
> locally on that developer's machine so it would not "interfere" with
> anybody else.
>
> Upon startup, pax-ConfigAdmin would first check for the existence of
> such optional file. If it exists, these would override the props of
> the default file. Otherwise, it would use the props in the default
> file (if any).
Not sure if you are referring to the simple "properties bootstrapping
configuration agent" or the more advanced "ConfMan" that has been taken out
of projects/pax/ for now.
For the former we seem to have been identified;
1. Factory properties that never changes.
2. Application properties that are shared across instances.
3. Properties that survives reboots.
4. Some properties are written back to the original files.
5. Properties to be loaded when there is a solar eclipse.
6. Propertoes to be loaded when the operator wears a green hat, jump
on one leg holding his right ear with the left hand....
Ok, where does it stop??
For the latter case;
Configuration Admin Agent (ConfMan), does not use properties files, but
BeanShell scripts. This is so people easily can write their own logic or
reading arbitrary file formats. However, there is currently no "triggering"
mechanism that is available to the Beanshell script as far as I know, so that
could be a thing to consider.
That would make the above list almost possible, and no decision has to be made
on where things stop...
Cheers
Niclas
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
