karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jb@nanthrax.net ...@nanthrax.net>
Subject Re: Bundle start level
Date Thu, 17 Oct 2019 11:57:24 GMT


First of all, generally speaking, start level is not a good idea. Your bundles should be dynamic
enough to track service, etc.

Back on start level:

1. if your bundle is a startup bundle (defined in etc/startup.properties), the start level
is defined there.
2. it's also possible to specify the start level on the features.xml and on the feature itself

It's mostly matter for boostrap.


On Thursday, October 17, 2019 13:46 CEST, Patrique Legault <patriquelegault@gmail.com>
 Depends on how you install the bundle.

If you use features you can use "start-level" tag in the feature xml. This
will force start the bundle once that level is ready.

You can also put dependencies between features, as in dont stary X until Y
is started.

Here is more examples and info.

On Thu., Oct. 17, 2019, 1:37 p.m. leonardchicco, <
luca.leonardi1974@gmail.com> wrote:

> Good morning,
> It's possible to force a startlevel for a custom bundle during the first
> startup when the data folder is empty?
> For example i need to start a bundle with start level 257?
> Or for example after feature quartz?
> In attacment my definition pom for custom distribution. pom.xml
> <http://karaf.922171.n3.nabble.com/file/t498205/pom.xml>
> Thanks in advance
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message