BUNDLES that can be dynamically installed, started, paused, UPDATED, and deleted are added by the OSGi Life-Cycle layer. The security architecture protects all aspects of the life cycle.

The OSGi LIFECYCLE can be broken down into the following steps:

• INSTALLED- The bundle has been installed in the OSGi container, but some of its dependencies have still to be satisfied. The bundle requires packages that haven't been exported by any of the other bundles that are presently installed.
• RESOLVED- The bundle has been installed, and the OSGi system has connected and resolved all of the dependencies at the class level. The bundle is now ready to use. When a bundle is started, it skips this state if all of the bundle's dependencies are met.
• STARTING -It is the temporary state in which the bundle exists while it is being loaded after all dependencies have been resolved. The BundleActivator.start METHOD will be invoked, but it hasn't returned YET.
• ACTIVE - The bundle is active, however, it is disabled while Spring is working. Spring examines the Spring setup and creates the context before passing it on to the plugin. In order to make instances of each plugin module, the plugin requires context.
• STOPPING - It is a brief state in which the bundle is in when it is stopping. Although the BundleActivator.stop function has been called, it has yet to return.
• UNINSTALLED - The bundle has been removed from the OSGi container.