You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/04/18 15:28:25 UTC

[jira] [Created] (JCRVLT-116) InstallHookProcessor.Hook should not only use TCCL as fallback

Konrad Windszus created JCRVLT-116:
--------------------------------------

             Summary: InstallHookProcessor.Hook should not only use TCCL as fallback
                 Key: JCRVLT-116
                 URL: https://issues.apache.org/jira/browse/JCRVLT-116
             Project: Jackrabbit FileVault
          Issue Type: Improvement
    Affects Versions: 3.1.26
            Reporter: Konrad Windszus


Currently the {{InstallHookProcessor.Hook}} only uses the thread context class loader as fallback to load the hook classes (https://github.com/apache/jackrabbit-filevault/blob/64caa29325452c1adf968ae05e2308b37f3600cc/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/InstallHookProcessorImpl.java#L206). This almost never works in an OSGi context.

Instead I would propose to try the Bundle's Class Loader and add `DynamicImport-Package: *` to the OSGi manifest. 
That of course would not work in non-OSGi contexts. Therefore it should just be implemented as another fallback option (in addition to TCCL).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)