[kepler-dev] [Bug 3948] New: - Configuration systems should be merged

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: Configuration systems should be merged
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: core
        AssignedTo: berkley at nceas.ucsb.edu
        ReportedBy: berkley at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


Kepler currently has at least 4 different configuration systems each using
their own configuration file.  This makes it really difficult to figure out
where a specific configuration item is stored.  These systems should be merged
into, ideally, one system.  Realistically, however, two systems will probably
need to exist.  Currently all UI related configurations are done in .properties
files with standard java localization.  Workflow and core configuration is done
with the ptolemy configuration system.  Various other actors and subsystems use
their own configuration systems.  

Since kepler 2.0 will support modular additions to kepler, the configuration
system needs to be flexible enough to allow the modules to add configuration
items into the system at runtime.  The ptolemy configuration system is flexible
enough to do this and since it is used by the kernel, I propose keeping it as
the main config system.  I also propose keeping the .properties system for UI
specific options.  

Kepler, possibly through the module manager or possibly through a new
configuration manager, should provide an API for allowing modules to merge
their configuration options.  It should provide error handling for any
conflicts.  

An extensive search will need to be done on the standard modules to find any
other configuration subsystems being used and to merge them into the
appropriate new system.