@Named vs. @ManagedBean in JSF 2.0

A lot of people seem to suggest that you should use @Named instead of @ManagedBean in JSF 2.0 (e.g. see @ManagedBean dead on arrival? or this JavaRanch discussion).

However, what I discovered in a painful process is that you must use @ManagedBean when the scope is @ViewScoped, apparently because CDI doesn’t declare a view scope. Thus this is correct:

import javax.faces.bean.ManagedBean;
import javax.faces.bean.ViewScoped;

public class DogsBean {
// ...

NOTE: I am using JBoss 6 M3.


  1. Another thing I've noticed (although it might just be a problem on my end as I'm new to JSF) is that ajax-induced valueChangeHandlers will work with ManagedBeans but not @Named resources.

  2. I really can't wait to seeing this Dying to Read post and of course as always I have to give credit to the lovely Jill over at Breaking the Spine, which is so inspires me a lot as well. But there are also very beneficial human resources assignment help is always here to giving you their best services in all over the UK respectively.

  3. This is an amazing, I truly can't wait to visit this Dying to Read post and of study, as ever I keep giving glory to the beautiful Jill over at Cracking the Spine, which encourages me a lot as well I know best wiki writers for hire. they gives unbelievable services all over the US.

  4. I have noticed some writing issues in this post which can only be corrected by expert online book ghostwriters. By the way, I am really excited to read this Dying to Read post. As usual, I must give credit to the lovely work of these writers at breaking the spine, as her work greatly inspires me.