[
https://issues.apache.org/jira/browse/STANBOL-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-140.
-----------------------------------------
Resolution: Fixed
Finally completed by adding support for uninstalling resources installed for a
bundle if a bundle is stopped.
> Support for installing/configuring Stanbol Components based on data within an
> archive (including a Bundle)
> ----------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-140
> URL: https://issues.apache.org/jira/browse/STANBOL-140
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer, Entity Hub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
