You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2012/09/23 20:00:07 UTC

[jira] [Commented] (KARAF-1245) blueprint deployer and spring deployer should get started before features.core bundle

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

Christian Schneider commented on KARAF-1245:
--------------------------------------------

I think the feature install now waits for some time for missing url handlers. Does this fix the problem? I am also working on parallelizing the install of bundles. This will help if the url handler appear after a bundle they should install. See kARAf-608. I will explain what I have in mind there shortly.
                
> 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