Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

CODI provides default values via CDI beans. Therefore, it's possible to provide an alternative bean (via the std. @Specializes or @Alternative mechanism and the corresponding config specified provided by CDI). An alternative implementation is allowed to extend the default implementation - so it's possible just to override the values you have to customize. Or you just implement the corresponding interfaces and so you have to provide all values. Furthermore, there are add-ons e.g. for using the web.xml for the configuration (see External Resources).

Detailed information is available as JavaDoc at the corresponding interfaces.
Tipnote
titleHint
v0.9.2+

With CODI v0.9.2+ we made it easier for users to customize just single values. The default implementations are already available in the API modules (instead of the interfaces). So you have to use extends instead of implements and only the customized values are required.

Example (CODI v0.9.2+)

Code Block
java
java
titleCustom config which overrides the default value

@Specializes
@ApplicationScoped
public class CustomConversationConfig extends ConversationConfig
{
    @Override
    public int getConversationTimeoutInMinutes()
    {
        return 45;
    }
}

CodiCoreConfig (since 0.9.2)

  • isAdvancedQualifierRequiredForDependencyInjection

WindowContextConfig

  • isUrlParameterSupported
  • isUnknownWindowIdsAllowed
  • getWindowContextTimeoutInMinutes
  • getMaxWindowContextCount
  • isCreateWindowContextEventEnabled
  • isCloseWindowContextEventEnabled

...