Your browser does not support iframes
...
| Note | ||
|---|---|---|
| ||
If you would like to test CODI or you need all modules provided by CODI, you can use an all-in-one JAR file. |
This event gets fired as soon as the whole environment (e.g. CDI, JSF, CODI) is ready. In case of JSF this event is fired lazily.
Register a custom StartupEventBroadcaster for integrating a broadcaster which gets invoked before the StartupEvent was fired.
Attention: There is no guarantee that CDI has been bootstrapped.
However, a StartupEventBroadcaster allows to do it (see the controlled bootstrapping add-on).
The core of CODI provides base implementations which are used to provide a testable, pluggable and type-safe config. If it is possible this CDI based config approach is used to configure the framework (esp. the SPI). This approach decouples the logical config entries from the config-source. That means it's possible to switch e.g. between Java Config (values are directly encoded in config classes), property files, db table/s, xml (e.g. web.xml) and every other format which can be used for a config.
...
