backing-beans

I came across the terms "managed bean" and "backing bean" in several forums. Many people think both are the same. But, there seems to be a slight difference. Can any one help me to understand the exact difference between these two terms? Changing my initial answer - there is no meaningful difference between the two. The tutorial says that backing beans are later declared as managed beans. So, to summarize: a backing bean is the class out of context a managed bean is the backing bean whenever it is declared to be used with the JSF managed bean facility. I've never actually used the term

I have a Facelet that might be used in different applications. I don't to copy it, but reuse it. I need to pass the backing bean that will manage the view as a parameter, as some logic may vary according to the application where it is used in. I don't want to use a composite component, but just include the Facelet and specify which bean will manage the view. How can I achieve this? Let me give an example: <ui:composition template="/resources/common/templates/template.xhtml" xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns

Does it make sense to use Entities as JSF Backing Beans? @Entity @ManagedBean @ViewScoped public class User { private String firstname; private String lastname; @EJB private UserService service; public void submit() { service.create(this); } // ... } Or is it better to keep them separately and transfer the data from the backing bean to the entity at the end? @ManagedBean @ViewScoped public class UserBean { private String firstname; private String lastname; @EJB private UserService service; public void submit() { User user = new User(); user.setFirstname(firstname); user.setLastname(lastname);