karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-1245) blueprint deployer and spring deployer should get started before features.core bundle
Date Fri, 09 Mar 2012 08:46:54 GMT

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

Jean-Baptiste Onofré commented on KARAF-1245:
---------------------------------------------

Nevermind, the deployers should be in the startup.properties, else the features.core will
always be started before.

I move the deployers into the startup.properties.
                
> 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: Jean-Baptiste Onofré
>             Fix For: 2.2.6
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message