[ https://issues.jboss.org/browse/JBIDE-16947?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-16947 at 3/31/14 9:17 PM: ------------------------------------------------------------------------ To revalidate injection of a bean, we have to know that something in that bean is changed. If change is indirect, because of a change in a third file, we have to keep dependency of the bean's resource on that file. In the case of exact type name we easily can add dependency of 'exclude.p1.Bean2' on beans.xml, and I suggest that we do it. But if one adds to beans.xml <weld:exclude name="exclude.p1.*"/>, then we have to scan the package and add dependency of all resources on beans.xml - that can be time consuming. was (Author: scabanovich): To revalidate injection of a bean, we have to know that something in that bean is changed. If change is indirect, because of a change in a third file, we have to keep dependency of the bean's resource on that file. In the case of exact type name we easily can add dependency of 'exclude.p1.Bean2' on beans.xml, and I suggest that we do it. But if one adds to beans.xml <weld:exclude name="exclude.p1.*"/>, then we have to scan the package and add dependency of all resources to beans.xml - that can be time consuming. -- 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