[kepler-dev] [Bug 4394] - Need to develop requirements for configuration subsystem

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4394





------- Comment #6 from jones at nceas.ucsb.edu  2009-09-28 11:39 -------
Correct, there is no concept of permissions.  We discussed this, and decided it
would be essentially impossible for a module author to determine ahead of time
how another module might want to interact, and therefore really not feasible to
declare properties as private to a module without compromising extensibility.

There is, however, a concept of 'mutable', which allows a module to mark a
property as one which is/should be monitored at runtime for changes, and the
application will respond appropriately without restart.  If a property is not
marked as 'mutable', then other modules should assume a Kepler restart is
needed for their property change to take effect.  If it is mutable, then they
can assume property changes take effect at the time of the change, and they
should be careful to monitor further property changes that might affect them at
runtime using the listener interfaces.