DZone
Java Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Java Zone > Using @Named vs. @ManagedBean

Using @Named vs. @ManagedBean

Determining the best annotations to use for controlling JSF apps using different web containers.

Martin Farrell user avatar by
Martin Farrell
·
Aug. 29, 16 · Java Zone · Tutorial
Like (3)
Save
Tweet
26.85K Views

Join the DZone community and get the full member experience.

Join For Free

I was looking through some JSF controllers and it was a mix of @Named and @ManagedBean annotations. These annotations provide similar dependency injections, but there are important differences.

Containers

  • @ManagedBean – javax.faces.bean.ManagedBean – managed by JSF container
  • @Named – javax.faces.bean – CDI bean managed by application server

This means @Named beans are visible to the whole JEE container, while @ManagedBean are visible only to the JSF container. The visibility issue is covered in this table:

Inject @Named@ManagedBean
@NamedYY(*)
@ManagedBeanN

Y(*)

* – only if scope of injected bean is broader

One problem is that @Named requires that you use a JEE enabled container – so you have to use TomEE instead of Tomcat.

Scope

A further problem in earlier CDI versions was that there was no CDI equivalent of @ViewScoped. This has now been resolved with  @javax.faces.view.ViewScope.

You also need to be very careful with mixing JSF and CDI as they use different packages – javax.faces.bean vs. javax.enterprise.context.

So What Approach Should You Use?

This is a non-question as from JSF2.3 onwards @ManagedBean is being phased out and the recommended approach is @Named. It is also important not to mix CDI with JSP scopes

However there are circumstances when I would still use @ManagedBean at present:

  • Existing Code is using @ManagedBean – I would stick with @ManagedBean until a migration path is determined
  • Web Container – You just want to use a web container – then sticking with JSF ManagedBeans would be easier

Reference

http://germanescobar.net/2010/04/4-areas-of-possible-confusion-in-jee6.html

Web container

Published at DZone with permission of Martin Farrell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • 5 Options for Deploying Microservices
  • Build a Serverless URL Shortener With Go
  • The Web Performance APIs Reference
  • DevOps Security Checklist for Kubernetes

Comments

Java Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo