[jira] [Commented] (JCRVLT-195) Support OSGi bundle dependencies

["Tobias Bocanegra (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCRVLT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243411#comment-16243411 ] 

Tobias Bocanegra commented on JCRVLT-195:
-----------------------------------------

bq. Only that way it can be assured, that the installation of this package is deferred until that bundle providing the hook is finally active. 

[~kwin] how should this work? I assume you install a super package via http or package manager. the package contains various sub-packages and bundles. and one of the sub-packages contains a hook that needs the bundle. so now you want the entire installation to sleep until the bundle is active?

{noformat}
super-pkg
  |- hook-pkg
  |- bundle-with-hook
{noformat}

*or* are you using the OSGi package installer and need to ensure the proper dependency resolution there? (this would rather be a granite / sling issue)


> Support OSGi bundle dependencies
> --------------------------------
>
>                 Key: JCRVLT-195
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-195
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Konrad Windszus
>            Assignee: Tobias Bocanegra
>             Fix For: 3.1.42
>
>
> FileVault Packages support both internal and external hooks. Internal hooks are JARs which are part of the package itself. External hooks are provided through some classloader (usually through the Bundle Classloader in an OSGi context, https://issues.apache.org/jira/browse/JCRVLT-116). Installing a package depending on an external hook class which is not found, leads to an error.
> Therefore it would be beneficial to explicitly add a dependency from the package referencing an external hook towards the OSGi bundle providing the hook. Only that way it can be assured, that the installation of this package is deferred until that bundle providing the hook is finally active. Currently only package dependencies are supported though, which are not enough, as there is a delay until the embedded bundle in a package is deployed as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)