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.
Java EE 6 newcomer question ahead, so beware…
I keep reading introductory CDI material like
http://docs.jboss.org/cdi/spec/1.0/html_single/#d0e268
I’m wondering throughout that document why they are mixing @SessionScoped with @Model, which is defined as being @RequestScoped plus @Named and a few other things I don’t understand.
Why aren’t the beans, e.g. the Login bean, simply annotated with @Named + @SessionScoped? What’s the gain here?
Thanks
You’re right using
@Named@SessionScoped`would achieve the same and would be clearer. In fact I wonder if some CDI impl couldn’t throw an exception with this double scope (Weld doesn’t).BTW I encourage you to read Weld documentation which is a more concrete approach to CDI IMHO.