Child pages
  • Dynamic Configurations

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


Lyncode is developing a new implementation for the ConfigurationManager. Features:

  • Dynamic configurations (runtime changes)
  • Improved API (


  • omission handling)
  • Derived values support
  • Modules support
  • File Based

We also think that modules should be replaced by contexts, that is, conceptually modules must be included by the main object (configuration file). So our proposal is going to work much like apache 2 configuration, it will use the properties syntax, and replace the actual concept of modules (that allows contextualization of properties) by the concept of Context (a new syntax addition).

NOTE: Our team have internally discussed about a database based implementation (, but it would have conceptual problems. Mainly:

  • How to get the database configuration? (it must be placed somewhere - not in the database)
  • Reading configurations from there will put an avoidable extra task on top of the DB
  • On database crashes, some services (that, today, do not use database at all), will also crash
  • Derived values aren't advisable (it would make many SQL queries to get a simple configuration value)

API Changes : New available methods

String ConfigurationManager.getString(String key, String default);
String ConfigurationManager.getString(String module, String key, String default);
List<String> ConfigurationManager.getList(String key);
List<String> ConfigurationManager.getList(String module, String key);

Core Changes : New possible features

It's now possible to easily set/add properties and save the respective files, also it's easy to access and modify the properties description.

Pull Request

NOTE: The under development SpringUI and its associated features made us recognize that, changing the core ConfigurationManager, is an important change to make DSpace more user friendly in the future.