...

See Pre-required readings

Further readings:

• SPIs and common customizations
• DevDoc

Usage for Users

ProjectStage

...

In some cases it isn't possible to use CDI based configuration. Esp. for parts which have to be active before the CDI container gets bootstrapped.
For such cases CODI uses an extensible configuration approach. By default it supports configuration via:

• ServiceLoader (if classes have to be configured which implement an interface or extend an abstract class)
• System properties
• JNDI
• Resource Bundle (properties file with the name myfaces-extcdi.properties btw. /META-INF/myfaces-extcdi.properties)

However, with a custom ConfiguredValueResolver it's possible to resolve configured values from any kind of configuration-source.

...

The following events are optional and have to be activated via the configs mentioned above.

• AccessBeanEvent
• CloseConversationEvent
• CloseWindowContextEvent
• CreateWindowContextEvent
• RestartConversationEvent
• ScopeBeanEvent
• StartConversationEvent
• UnscopeBeanEvent

Security

CODI provides some basic hooks to integrate a custom security concept. It isn't related to an existing framework. CODI just allows to integrate such frameworks based on the ViewConfig or via interceptors.

...