Java Reference
In-Depth Information
->
install file:foo.jar
Bundle: 3
->
start 3
->
bundles
ID State Name
[ 0] [ ACTIVE] System Bundle
Location: System Bundle
Symbolic-Name: system.bundle
[ 1] [ ACTIVE] Simple Shell
Location: file:org.foo.shell-1.0.jar
Symbolic-Name: org.foo.shell
[ 3] [INSTALLED] Foo Bundle
Location: file:foo.jar
Symbolic-Name: org.foo.foo
->
startlevel 2
->
bundles
ID State Name
[ 0] [ ACTIVE] System Bundle
Location: System Bundle
Symbolic-Name: system.bundle
[ 1] [ ACTIVE] Simple Shell
Location: file:org.foo.shell-1.0.jar
Symbolic-Name: org.foo.shell
[ 3] [ ACTIVE] Foo Bundle
Location: foo.jar
Symbolic-Name: org.foo.foo
->
bundlelevel 3 3
->
bundles
ID State Name
[ 0] [ ACTIVE] System Bundle
Location: System Bundle
Symbolic-Name: system.bundle
[ 1] [ ACTIVE] Simple Shell
Location: file:org.foo.shell-1.0.jar
Symbolic-Name: org.foo.shell
[ 3] [ RESOLVED] Foo Bundle
Location: file:foo.jar
Symbolic-Name: org.foo.foo
In this example session, you first use the
startlevel
command to display the frame-
work's current active start level, which is 1 by default. You use the
bundlelevel
com-
mand with the
-i
switch to set the initial bundle start level of installed bundles to 2.
Subsequently, when you install and start the
foo
bundle, you can see from the follow-
ing
bundles
command output that it's not started yet. This is expected, because the
bundle's start level is 2, but the framework's active start level of 1 is less than that. You
raise the framework's active start level to 2, which ultimately causes the
foo
bundle to
be started. Using the
bundlelevel
command to set the
foo
bundle's start level to 3
stops the bundle again.
That's all there is to the Start Level Service. You'll not likely need this service often,
because bundle activation ordering isn't good practice, but it can come in handy in
certain situations. We've finished covering application management; let's summarize
what we've discussed.
