Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When developing a Java EE application, it is possible to use EJBs as controllers?
The EJB container provides features such as lifecycle management, and concurrency control, Is it correct create a stateless EJB to be a controller and injects it into a ManagedBean?
From EJB 3.0 and specially in 3.1, the EJB Beans become more and more POJOs thus the EJB concept blurs in favor of the more generic Managed Bean concept, inside the CDI. Even the
@EJBannotation “competes” with@Injectand could eventually be replaced by it.So in CDI, a controller can be a managed bean and take advantage of the Java EE server features like lifecycle management and such.