[STANBOL-140] Support for installing/configuring Stanbol Components based on data within an archive (including a Bundle)

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Component/s: Enhancer, Entityhub
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 03/Apr/11 20:55
• Updated: 02/May/13 02:29
• Resolved: 18/Jul/11 21:09

Description

As an example to initialize a Entityhub referenced site with a local cache it is necessary to configure

• the ReferencedSite (OSGI component configuration)
• a cache (OSGI component configuration)
• a yard - local storage component (OSGI component configuration)
• install the precomputed data of the index (archive with the data of the index)

To avoid that users need to deal with several artifacts to install a single component Stanbol should support to install/configure multiple components based on configuration data within an archive.

The current plan is to support two variants:
(1) Bundles: By using the OSGi extender pattern (as described at [1]) installed Bundles are scanned of they contain files that need to be installed.
(2) Jar files that are copied by the user to a special directory. This will also use the extender pattern.

The current plan is to implement this functionality based on the Apache Sling installer. See this email thread [2] for additional context.

[1] http://www.aqute.biz/Snippets/Extender
[2] http://markmail.org/thread/w2s7h3rcnkc2zlzm

Issue Links

• is depended upon by: STANBOL-287 Support Removal of SolrIndexes installed based on Configurations/Files managed by the Sling Installer
• is related to: STANBOL-92 package solr index for popular entities
• is related to: STANBOL-93 package solr index for popular topics
• is related to: STANBOL-141 Support for installing Solr Indexes form Archives