[
https://issues.jboss.org/browse/JBIDE-16947?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-16947:
-----------------------------------------------
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.
Beans are not automatically validated when beans.xml is changed
---------------------------------------------------------------
Key: JBIDE-16947
URL:
https://issues.jboss.org/browse/JBIDE-16947
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.2.0.Beta1
Reporter: Rastislav Wagner
Assignee: Alexey Kazakov
Fix For: 4.2.x
When beans.xml file is changed we always have to run validation manually to reflect
newest changes. Shouldn't this be done automatically after beans.xml is changed and
saved?
--
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