title: Difference between a managed bean and a session bean
body: <p>Say I have an Entity class, Car.&nbsp;</p>
  
  <pre><code>@Entity
  public class Car
  </code></pre>
  
  <p>My IDE lets me automatically generate session beans from entity classes, so I end up with a CarFacade</p>
  
  <pre><code>@Stateless
  public class CarFacade
  </code></pre>
  
  <p>I can also generate JSF Managed beans</p>
  
  <pre><code>@ManagedBean     
  @RequestScoped
  public class RegistrationController
  </code></pre>
  
  <p>I can understand the meaningful difference between the Entity class and other beans, but what are the differences between a stateless session bean and a managed bean? I read that a stateless session bean is for implementing your business logic that operates on the entities and managed beans are for interacting with the web-based front-end, by having the webpage call methods on the managed bean, and having the managed bean call business methods on the session bean.</p>
  
  <p>So in my example, the RegistrationController would feature a +register(String carRegistration) method that the webpage would call. The RegistrationController would in turn instantiate a Car and call +create(Car car) on the session bean, which would persist it.</p>
  
  <p>Is this correct?</p>