In fact, these are two distinct problems. First BeanA does not have an appropriate constructor and so it's not registered as a bean. We don't log or record this kind of incidents as it does not necessarily have to be an error. Also note that usually there will a lot of classes which do not meet conditions from "3.1.1. Which Java classes are managed beans?". Consequently, there is an unsatisfied dependency for the required type BeanA and the qualifier Default. I think it would be quite complicated to track and analyze all the problems only to produce a more specific problem description (something like: "Unsatisfied dependency because of BeanA does not declare an appropriate constructor").

What we could probably do is to log a warning if a class which is explicitly annotated with a scope has a similar problem. Tomas Remes Tom, could you look at it?