[
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108619#comment-16108619
]
Christian Schneider commented on KARAF-4261:
--------------------------------------------
Start levels are not a good way to control the order in OSGi. Have you tried to
create a service depdendency? That ususally works better.
Your data access bundle should provide an OSGi service that higher level
bundles use.
> Bundle start-level seems to be ignored at Karaf restart
> -------------------------------------------------------
>
> Key: KARAF-4261
> URL: https://issues.apache.org/jira/browse/KARAF-4261
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-kar
> Affects Versions: 4.0.3
> Reporter: Ralf Steppacher
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.2, 4.0.10
>
>
> AS a workaround for CAMEL-9483 I have set a start-level for my bundles
> deployed as part of my features. This works as expected during initial
> deployment (order of deployment is according to the start levels I set), but
> not during sub-sequent starts of Karaf. It appears the start-level of the
> bundles is ignored, meaning the order of deployment of my bundles is more or
> less random and I observe the issues described in CAMEL-9483 again.
> {{bundle:list}} shows my bundles with the start-levels they have been
> originally deployed with, though.
> As a workaround I set {{karaf.clean.all = true}} in system.properties.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
