[kepler-dev] [Bug 3948] - Create new configuration system supporting modules

[bugzilla-daemon at ecoinformatics.org]

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





------- Comment #5 from berkley at nceas.ucsb.edu  2009-09-11 10:27 -------
After looking at Matt's UML diagram
(https://code.kepler-project.org/code/kepler-docs/trunk/teams-and-wg/2-infr-teams/framework/design/configuration/configuration-architecture.png),
I've been thinking about a couple ideas for serialization.  The config system
will need to serialize/deserialize to multiple different locations.  I think
this should use the build system's moduleTree functionality.  The workflow
would look something like this:

deserialize:
for each module in moduleTree
{
 get file module.config
 read module.config into common.config
}

serialize:
for each module.namespace in common.config
{
  find module.namespace in common.config
  write module.namespace to module.config
} 

The moduleTree functionality is in the build system jar that is accessible from
the kepler runtime.  

Instead of using a String to represent a module in the ConfigurationProperty,
we should probably use a Module object like the build system does.  That way,
the configuration system has all of the module's metadata that is read in at
startup.  This could be a useful way for other modules or the core to get
information on modules at runtime.