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.
Section 5.4.1 of the CDI spec states that otherwise valid beans are unproxyable (and thus cannot be injected) if declared final. The spec gives no rationale and I can not think of a reason for this decision.
I am trying to stick by design rules saying that classes not explicitly designed for inheritance should forbid it. So the CDI spec seems to enforce bad design (and makes CheckStyle cry).
Why is it so and what can be done about it?
Thank you.
Because when you create a proxy for a class you inherit from it (or implement an interface, if possible) so if your class is final it can not be inherited from and no proxy can be created for it.
If you want to use CDI you need to have a non-final class. The other option is not use CDI altogether.