[weld-issues] [JBoss JIRA] (WELD-964) Unsatisfied dependency exception should differentiate between "class is not in classpath", "class is in classpath but not managed bean" and "class is in classpath and managed but not like that"

Tue, 30 Jul 2013 01:35:45 -0700

Pull request is at https://github.com/weld/core/pull/339

I did not implement things as requested here, because it just isn't appropriate. I did what I could:

  • if a class X is ignored because it has a reference to class Y and Y is missing from the classpath, the exception will now say that X was ignored because Y was not found,
  • if the injection point could be satisfied if it had no qualifiers, the exception will list all beans that are assignable to the injection point (but don't have the matching qualifiers)

I could not make the exception say "there is class X on the classpath, but there is no beans.xml", because it's possible that the class used at injection point is NOT inside a bean archive, but the bean itself is and isn't being injected for other reasons. Therefore, if the exception said "class X is on the classpath, but not in a bean archive", the message would be misleading.

Also, the first option as described in the description of this task, is not possible, since if the class used at injection point is not on the classpath, the bean declaring this injection point will be ignored and the injection point won't even be validated.
Change By: Marko Lukša (30/Jul/13 4:33 AM)
Status: Open Pull Request Sent
Git Pull Request: https://github.com/weld/core/pull/339
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira 
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues

Reply via email to