[cdi-dev] [JBoss JIRA] (CDI-473) Standardize eager initialisation of ApplicationScoped bean

Antonin Stefanutti (JIRA) issues at jboss.org
Mon Sep 15 05:54:02 EDT 2014

Antonin Stefanutti created CDI-473:

             Summary: Standardize eager initialisation of ApplicationScoped bean
                 Key: CDI-473
                 URL: https://issues.jboss.org/browse/CDI-473
             Project: CDI Specification Issues
          Issue Type: Feature Request
          Components: Contexts
            Reporter: Antonin Stefanutti

Given the proxying strategy documented in the CDI specification, normal scoped beans get initialize when an injected proxy reference is first called.

While that's perfectly fine in the vast majority of use cases, that proves inconvenient when dealing with {{ApplicationScoped}} beans that capture application singletons which we want to bound to the application lifecycle with a {{postConstruct}} callback. As this callback is only called when a proxy is invoked, it is frequent to see the application developers using a CDI extension to meet that need, e.g.:

void forceInitialization(@Observes AfterDeploymentValidation adv, BeanManager manager) {
    for (AnnotatedType<?> type : eagerBeans)
        // Calling toString is necessary to force the initialization of normal-scoped beans
        BeanManagerHelper.getReferencesByType(manager, type.getBaseType(), AnyLiteral.INSTANCE).toString();

There should be a concise way to declare that intent which would then be address by the CDI container, for example:
@ApplicationScoped(eager = true}
class EagerApplicationScopedBean {

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list