[
https://issues.apache.org/jira/browse/KARAF-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461643#comment-13461643
]
Christian Schneider commented on KARAF-1245:
--------------------------------------------
Yes .. but then we depend on the handlers .. I would like to find a solution
that can work with unknown handlers too. Basically the idea is to first load
bundles that do not need the handlers. We then need to start at least the
bundles with the handlers before starting the rest. The problem is that there
is no way to see if a bundle contains a handler from the outside. So I am not
sure how to achieve it.
> blueprint deployer and spring deployer should get started before
> features.core bundle
> -------------------------------------------------------------------------------------
>
> Key: KARAF-1245
> URL: https://issues.apache.org/jira/browse/KARAF-1245
> Project: Karaf
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Ioannis Canellos
> Fix For: 2.2.6, 3.0.0
>
>
> When org.apache.karaf.features.core bundle is up, it will load features
> descriptors and try install features, however if the features descriptor has
> bundle like
> <bundle>blueprint:file:etc/some-blueprint.xml</bundle>, we need blueprint url
> handler available in the OSGi container, so we need blueprint deployer and
> spring deployer get started before features.core bundle
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
