You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2015/08/17 11:36:46 UTC

[jira] [Updated] (OAK-3194) Provide a way for embedding application to control which all bundles are started

     [ https://issues.apache.org/jira/browse/OAK-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella updated OAK-3194:
----------------------------------
    Fix Version/s:     (was: 1.3.5)
                   1.3.4

> Provide a way for embedding application to control which all bundles are started
> --------------------------------------------------------------------------------
>
>                 Key: OAK-3194
>                 URL: https://issues.apache.org/jira/browse/OAK-3194
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: pojosr, webapp
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.3.4
>
>
> Felix Connect OSGi support currently scans the whole classpath to find out which all bundles to be started. In Application server deployment this may pickup jars from parent classloader which might have OSGi headers and there activators might get invoked. This might lead to undesired effects.
> Instead the {{ClasspathScanner}} supports a filter to allow selecting which all bundles should be selected from a given scan. {{OakOSGiRepositoryFactory}} should allow specifying of this filter in parameters map



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