Backing beans (@ManagedBean) or CDI Beans (@Named)?

by

Use CDI.

As per JSF 2.3, @ManagedBean is deprecated. See also spec issue 1417. This means that there’s not anymore a reason to choose @ManagedBean over @Named. This was first implemented in Mojarra 2.3.0 beta version m06.

enter image description here

History

The core difference is, @ManagedBean is managed by JSF framework and is only via @ManagedProperty available to another JSF managed beans. @Named is managed by application server (the container) via CDI framework and is via @Inject available to any kind of a container managed artifact like @WebListener, @WebFilter, @WebServlet, @Path, @Stateless, etc and even a JSF @ManagedBean. From the other side on, @ManagedProperty does not work inside a @Named or any other container managed artifact. It works really only inside @ManagedBean.

Another difference is that CDI actually injects proxies delegating to the current instance in the target scope on a per-request/thread basis (like as how EJBs are been injected). This mechanism allows injecting a bean of a narrower scope in a bean of a broader scope, which isn’t possible with JSF @ManagedProperty. JSF “injects” here the physical instance directly by invoking a setter (that’s also exactly why a setter is required, while that is not required with @Inject).

While not directly a disadvantage — there are other ways — the scope of @ManagedBean is simply limited. From the other perspective, if you don’t want to expose “too much” for @Inject, you can also just keep your managed beans @ManagedBean. It’s like protected versus public. But that doesn’t really count.

At least, in JSF 2.0/2.1, the major disadvantage of managing JSF backing beans by CDI is that there’s no CDI equivalent of @ViewScoped. The @ConversationScoped comes close, but still requires manually starting and stopping and it appends an ugly cid request parameter to outcome URLs. MyFaces CODI makes it easier by fully transparently bridging JSF’s javax.faces.bean.ViewScoped to CDI so you can just do @Named @ViewScoped, however that appends an ugly windowId request parameter to outcome URLs, also on plain vanilla page-to-page navigation. OmniFaces solves this all with a true CDI @ViewScoped which really ties the bean’s scope to JSF view state instead of to an arbitrary request parameter.

JSF 2.2 (which is released 3 years after this question/answer) offers a new fully CDI compatible @ViewScoped annotation out the box in flavor of javax.faces.view.ViewScoped. JSF 2.2 even comes along with a CDI-only @FlowScoped which doesn’t have a @ManagedBean equivalent, hereby pushing JSF users towards CDI. The expectation is that @ManagedBean and friends will be deprecated as per Java EE 8. If you’re currently still using @ManagedBean, it’s therefore strongly recommend to switch to CDI to be prepared for future upgrade paths. CDI is readily available in Java EE Web Profile compatible containers, such as WildFly, TomEE and GlassFish. For Tomcat, you have to install it separately, exactly as you already did for JSF. See also How to install CDI in Tomcat?

More Related Contents:

  1. Get JSF managed bean by name in any Servlet related class
  2. How to replace @ManagedBean / @ViewScope by CDI in JSF 2.0/2.1
  3. JSF does not populate @Named @RequestScoped bean with submitted input values
  4. Are @ManagedBeans obsolete in JavaEE6 because of @Named in CDI/Weld?
  5. How to choose the right bean scope?
  6. Identifying and solving javax.el.PropertyNotFoundException: Target Unreachable
  7. Differences between action and actionListener
  8. How to use PrimeFaces p:fileUpload? Listener method is never invoked or UploadedFile is null / throws an error / not usable
  9. Difference between h:button and h:commandButton
  10. How implement a login filter in JSF?
  11. Localization in JSF, how to remember selected locale per session instead of per request/view
  12. How do PrimeFaces Selectors as in update=”@(.myClass)” work?
  13. Packaging Facelets files (templates, includes, composites) in a JAR
  14. What is the usefulness of statelessness in JSF?
  15. What URL to use to link / navigate to other JSF pages
  16. PrimeFaces CSS skin not showing in login page, also JavaScript undefined errors
  17. How to update Mojarra version in GlassFish
  18. @Inject to pass params to a CDI @Named bean via URL
  19. Changing faces-config.xml from 2.2 to 2.3 causes javax.el.PropertyNotFoundException: Target Unreachable, identifier ‘bean’ resolved to null
  20. What is the function of @this exactly?
  21. Adding faces message to redirected page using ExternalContext.redirect()
  22. How to use EL in PrimeFaces oncomplete attribute which is updated during action method
  23. How create a custom converter in JSF 2?
  24. Primefaces valueChangeListener or
  25. JSF 2.0: How to override base renderers with custom ones?
  26. h:commandButton not working inside h:dataTable
  27. Uses of javax.faces.PROJECT_STAGE
  28. Redirect in @PostConstruct causes IllegalStateException
  29. Skip required validation and invoke the application
  30. How can I get a message bundle string from inside a managed bean?

Leave a Comment