...
It is often necessary to create a POJO object as soon the instance becomes valid (i.e. required services are available). It is also often needed to be able to stop it nicely. This pages presents the iPOJO capabilities to achieve such actions. iPOJO allows you to invoke methods (callbacks) on the POJO object when instance's state changed. For example, it allows invoking a start
method when the instance becomes valid and a stop
method when the instance becomes invalid. It allows the creation of immediate
component. This page presents how to use this handler.
Div | ||||||
---|---|---|---|---|---|---|
| ||||||
| ||||||
Wiki Markup | ||||||
{div:class=toc}
{toc:maxLevel=4|minLevel=2}
{div} |
Instance Lifecycle
iPOJO instances have a very simple lifecycle. This lifecycle contains two states: INVALID
and VALID
. Once an instance is created, this instance can only be valid if all its plugged handlers are valid. In the most basic case it means all required services are available. For example, an instance requiring a service (and so using the dependency handler) cannot be valid if the required service is unavailable.
...