karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Canellos (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (KARAF-1245) blueprint deployer and spring deployer should get started before features.core bundle
Date Tue, 11 Sep 2012 15:25:07 GMT

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

Ioannis Canellos reopened KARAF-1245:
-------------------------------------

      Assignee: Ioannis Canellos  (was: Jean-Baptiste Onofré)

I am reopening the issue, because I feel that the features service should not depend on deployers
of any short.

Moreover, the current solution may solve the problem for blueprint and spring url handlers,
but still doesn't address the case where the user wants to use a custom url handler.
                
> 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

Mime
View raw message