Application specific modules usually implement this interface to enable life-cycle support
Modules can do not have to implement this interface (modules can be plain Java Objects too) if
no dependencies exists.
Initialization phase TWO of the module. Its individual dependencies ARE met.
This is the main initialization phase and the module can use other modules, on which it depends.
Initialization phase TWO of the module. Its individual dependencies ARE met.
This is the main initialization phase and the module can use other modules, on which it depends.
Initialization phase TWO of the module. Its individual dependencies ARE met.
This is the main initialization phase and the module can use other modules, on which it depends.
Initialization phase ONE of the module. Its individual dependencies ARE NOT met.
To support multi-threading more efficiently, the module can prepare itself as much as possible at this point.
Initialization phase ONE of the module. Its individual dependencies ARE NOT met.
To support multi-threading more efficiently, the module can prepare itself as much as possible at this point.
Initialization phase ONE of the module. Its individual dependencies ARE NOT met.
To support multi-threading more efficiently, the module can prepare itself as much as possible at this point.
The module should activate itself if nessesary (depending on the application only few modules have to be started).
All Modules are already initialized when calling this method.
The module should activate itself if nessesary (depending on the application only few modules have to be started).
All Modules are already initialized when calling this method.