[STANBOL-529] Components should manage there own default configuration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 07/Mar/12 10:40
• Updated: 09/May/12 13:47
• Resolved: 11/Apr/12 09:59

Description

Currently the default configuration of Apache Stanbol is included within the Sling launcher and initialized during the first start of Stanbol by the Sling Launchpad Installer (org.apache.sling.launchpad.installer). This means that the default configuration is NOT managed on component (enhancer, entityhub, contenthub ...) level but globally by the launcher.

The proposal is to change this so that each component ("org.apache.stanbol.

{component}") would managed its own module ("org.apache.stanbol.{component}

.defaults") that uses [1] to provide the default configuration for the

{component}.

This would have the following advantages against the current solution (adding all the defaults to the 'resources/config' folder of the launcher)

* It would allow us to manage the default config within an component (e.g. enhancer, entityhub, contenthub ...).
* the defaults-module could be added to the bundle list of that component
* users that do not want to use the default config could just exclude the "o.a.s.{component}

.defaults" bundle and provide their own configuration.

• uninstalling "o.a.s. {component}

  .defaults" would cause the default configuration to be removed.

• we would no longer need to duplicate the defaults for the different launchers.

see also [2] for more background information in this.

[1] [1] http://svn.apache.org/repos/asf/incubator/stanbol/trunk/commons/installer/bundleprovider/README.md
[2] http://markmail.org/message/xtgucai5euytitxd