I have a Tomcat 6 JSF web application that I’d like to set up with CDI beans. I will have to convert the project to CDI gradually though.
My question is: can CDI beans and traditional JSF managed beans be injected into each other?
Thanks.
Share
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.
I have a Tomcat 6 JSF web application that I’d like to set up with CDI beans. I will have to convert the project to CDI gradually though.
My question is: can CDI beans and traditional JSF managed beans be injected into each other?
Thanks.
All JSF managed beans (JMB) either are CDI managed beans (CMB) automatically, or can be recognized as such using the beans.xml marker file. (The requirements of a CMB are set very low and basically just dictate the existence of a non-parameter constructor.)
This means that you should be able to use (read: inject) all JMBs with almost no extra effort.
However, problems will arise because JMBs use different scopes than CMBs (
javax.faces.*vs.javax.enterprise.*)These are best solved by registering a relative simple CDI-extension: When the CDI server (Tomcat for you) starts, it will raise a couple of events that you can observe – this is be the place where you can detect JMBs and convert them into correctly scoped CMBs.
But before you start hacking: All this has already been done by the Seam 3 Faces module. Simply put it in your classpath, and all JSF-scopes are bridged to CDI-scopes.