How do I force an application-scoped bean to instantiate at application startup?

by

My first thought was to use an old style ServletContextListener contextInitialized() method and from there use an ELResolver to manually request the instance of my managed bean (thus forcing the initialization to happen). Unfortunately, I can’t use an ELResolver to trigger the initialization at this stage because the ELResolver needs a FacesContext and the FacesContext only exists during the lifespan of a request.

It doesn’t need to be that complicated. Just instantiate the bean and put it in the application scope with the same managed bean name as key. JSF will just reuse the bean when already present in the scope. With JSF on top of Servlet API, the ServletContext represents the application scope (as HttpSession represents the session scope and HttpServletRequest represents the request scope, each with setAttribute() and getAttribute() methods).

This should do,

public void contextInitialized(ServletContextEvent event) {
    event.getServletContext().setAttribute("bean", new Bean());
}

where "bean" should be the same as the <managed-bean-name> of the application scoped bean in faces-config.xml.

Just for the record, on JSF 2.x all you need to do is to add eager=true to @ManagedBean on an @ApplicationScoped bean.

@ManagedBean(eager=true)
@ApplicationScoped
public class Bean {
    // ...
}

It will then be auto-instantiated at application startup.

Or, when you’re managing backing beans by CDI @Named, then grab OmniFaces @Eager:

@Named
@Eager
@ApplicationScoped
public class Bean {
    // ...
}

More Related Contents:

  1. How to choose the right bean scope?
  2. Identifying and solving javax.el.PropertyNotFoundException: Target Unreachable
  3. Get JSF managed bean by name in any Servlet related class
  4. How to send form input values and invoke a method in JSF bean
  5. Invoke JSF managed bean action on page load
  6. How do I process GET query string URL parameters in backing bean on page load?
  7. ViewParam vs @ManagedProperty(value = “#{param.id}”)
  8. Why are there different bean management annotations
  9. Accessing injected dependency in managed bean constructor causes NullPointerException
  10. JSF managed-bean EJB injection
  11. @javax.faces.bean.ManagedProperty in CDI @Named bean returns null
  12. How and when is a @ViewScoped bean destroyed in JSF?
  13. JSF managed bean naming conventions
  14. NullPointerException while trying to access @Inject bean in constructor
  15. JSF does not populate @Named @RequestScoped bean with submitted input values
  16. How to set -Dorg.apache.el.parser.COERCE_TO_ZERO=false programmatically
  17. Read resource bundle properties in a managed bean
  18. JSF 1.2: How to keep request scoped managed bean alive across postbacks on same view?
  19. Difference between managed bean and backing bean
  20. Calling Primefaces dialog box from Managed Bean function
  21. How can I get a message bundle string from inside a managed bean?
  22. JSF Controller, Service and DAO
  23. When should I use h:outputLink instead of h:commandLink?
  24. Retaining GET request query string parameters on JSF form submit
  25. Trying to understand immediate=”true” skipping inputs when it shouldn’t
  26. How to use in or to select multiple items?
  27. JPA Entity as JSF Bean?
  28. JSF + PrimeFaces: `update` attribute does not update component
  29. action is only invoked on second click
  30. Is Facelets page generated to Servlet as JSP generated to Servlet

Leave a Comment