This section presents the lifecycle of a bean bundle and how it impacts CDI and OSGi regular behaviors. Mostly bean bundles follow the same lifecycle than a regular bundle. There are only two new possible states and they do not modify the behavior from OSGi side.
This figure shows the two new states a bean bundle can be in. These states are triggered by two new
events and address the CDI container dependency resolution (i.e. services annotated @Required).
Figure 6.1. The bean bundle lifecycle
The regular OSGi lifecycle is not modified by the new Weld-OSGi states as they have the same meaning than the ACTIVE state from an OSGi point of view. They only add information about the validation of required service availability.