Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-16947

Beans are not automatically validated when beans.xml is changed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.0.Beta2
    • 4.2.0.Beta1
    • cdi
    • None
    • Hide

      1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1

      2. Open test.TestExcluded.java
      3. ASSERT: @Inject Bean2 bean2 contains no warning
      4. add to beans.xml <weld:exclude name="exclude.p1.Bean2"/>
      5. Save beans.xml
      6. Check test.TestExcluded.java. @Inject Bean2 bean2 should contain warning (No bean is eligible..)
      7. FAIL: Warning is missing
      8. Press Validate context menu item
      9. Java file now contains No bean is eligible... warning

      Show
      1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1 2. Open test.TestExcluded.java 3. ASSERT: @Inject Bean2 bean2 contains no warning 4. add to beans.xml <weld:exclude name="exclude.p1.Bean2"/> 5. Save beans.xml 6. Check test.TestExcluded.java. @Inject Bean2 bean2 should contain warning (No bean is eligible..) 7. FAIL: Warning is missing 8. Press Validate context menu item 9. Java file now contains No bean is eligible... warning

      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?

            scabanovich Viacheslav Kabanovich (Inactive)
            rawagner@redhat.com Rastislav Wagner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: