This topic has not yet been written. The content below is from the topic description.
5.4. Lifecycle Callbacks In addition to applying aspects to beans that we instantiate using the Microcontainer we can also add behavior during the deployment and undeployment process. As mentinoed in Section 4.3, “Direct Access�, a bean goes through several different states as it is deployed. These include: NOT_INSTALLED the deployment descriptor containing the bean has been parsed, along with any annotations on the bean itself. DESCRIBED any dependencies created by AOP have been added to the bean, and custom annotations have been processed. INSTANTIATED an instance of the bean has been created. CONFIGURED properties have been injected into the bean, along with any references to other beans. CREATE the create method, if defined in the bean, has been called. START the start method, if defined in the bean, has been called. INSTALLED any custom install actions that were defined in the deployment descriptor have been executed and the bean is ready to access. Important The CREATE and START states are included for legacy purposes. This allows services that were implemented as MBeans in previous versions of the Enterprise Platform to function correctly when implemented as beans in the Enterprise Platform 5.1. If you do not define any corresponding create/start methods in your bean, it will pass straight through these states. These states represent the bean's lifecycle. You can define a number of callbacks to be applied to any point by using an additional set of elements: applied when entering/leaving the DESCRIBED state applied when entering/leaving the INSTANTIATED state applied when entering/leaving the CONFIGURED state applied when entering/leaving the CREATE state applied when entering/leaving the START state applied when entering/leaving the INSTALLED state Like the and elements, the elements contain name and class attributes. The Microcontainer uses these attributes to create an instance of the callback class, naming it so that it can be used as beans enter or leave the relevant state during deployment and undeployment. You can specify which beans are affected by the callback using the classes attribute, as shown in Example 5.5, “Using the classes Attribute�.