Learning lifecycle - OSGi in Action - page 113

3 Each bundle in the graph in the RESOLVED state, including those that were
stopped, is unresolved and moved to the INSTALLED state. This means the bun-
dles' dependencies are no longer resolved.
4 Each bundle in the graph in the UNINSTALLED state is removed from the graph
and completely removed from the framework (is free to be garbage collected).
You're back to a fresh starting state for the affected bundles.
5 For the remaining bundles in the graph, the framework restarts any previously
ACTIVE bundles, which resolves them and any bundles on which they depend.
6 When everything is done, the framework fires an event of type Framework-
Event.PACKAGES_REFRESHED .
As a result of these steps, it's possible that some of the previously ACTIVE bundles
can no longer be resolved; maybe a bundle providing a required package was
uninstalled. In such cases, or for any other errors, the framework fires an event of
type FrameworkEvent.ERROR .
The following shell session shows how you can use the resolve and refresh com-
mands in combination to manage a system:

-> install file:foo.jar
Bundle: 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
[ 2] [INSTALLED] Foo Bundle
Location: file:foo.jar
Symbolic-Name: org.foo.foo
-> resolve 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
[ 2] [ RESOLVED] Foo Bundle
Location: file:foo.jar
Symbolic-Name: org.foo.foo
-> refresh 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

B

Resolves
bundle

C

Transitions bundle
to INSTALLED state