JSF managed bean naming conventions

by

There is no strict convention specified by JSF itself. I’ve seen the following conventions:

  • FooBean
  • FooBacking
  • FooManager
  • FooController
  • FooManagedBean

Or even just Foo which is then placed in a specific package like com.example.controller, com.example.backing or even com.example.view, etc.

I myself tend to use FooManager for application and session scoped beans (e.g. DataManager, UserManager, LocaleManager, etc) and just Foo, or as mandated by my current project, FooBacking (e.g. Login or LoginBacking) for request and view scoped beans, which are each usually tied to a specific <h:form> and/or view.

FooBean is too vague. Really a lot of classes can be marked as javabeans. JSF managed beans, JPA entities, EJBs, data transfer objects, value objects, etc. The Bean naming does not indicate the real responsibility of the class in any way. True, I use often public class Bean or MyBean in my generic code examples in blogs or forum/Q&A answers, but in real world you should avoid that.

FooManagedBean is IMO a poor name, it’s not only too long and ugly, but technically, a managed bean is an instance of a backing bean which is managed by some framework (JSF in this case). The class definition itself is really a backing bean, not a managed bean. So a FooBackingBean is technically more correct, but it’s still too long and the Bean part is a bit itchy.

Anyway, this is a pretty subjective question which can hardly be answered objectively with The One And Correct answer. It really doesn’t matter that much to me or anyone else what you makes of it, as long as you’re consistent with it throughout the entire project.

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. How do I force an application-scoped bean to instantiate at application startup?
  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. How to include another XHTML in XHTML using JSF 2.0 Facelets?
  23. Uploaded image only available after refreshing the page
  24. How to add placeholder attribute to JSF input component?
  25. Why was “immediate” attribute added to the EditableValueHolders?
  26. Fileupload and PrettyFaces and JSF 2.2 [duplicate]
  27. How to concatenate Strings in EL expression?
  28. java.lang.IllegalStateException at com.sun.faces.context.FacesContextImpl.assertNotReleased
  29. JSF: Mojarra vs. OmniFaces @ViewScoped: @PreDestroy called but bean can’t be garbage collected
  30. Skip required validation and invoke the application

Leave a Comment