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

Changing bean discovery mode doesn't run validation for existing beans

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.3.0.Alpha2
    • 4.2.0.Final, 4.2.1.Final
    • cdi
    • None
    • Hide

      1. Create CDI 1.1 project with discovery mode annotated
      2. Create two java classes (ie Bean1 and Bean2)
      3. add scope to Bean1 and inject Bean2
      ASSERT: warning is shown "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]"

      4. change discovery mode to all
      ASSERT: no warning is displayed in Bean1
      FAIL: warning is still present. You have to edit Bean1 to reflect new discovery mode.

      NOTE: This applies for all beans - if you have more, you have to edit all of them (or run validate)

      Show
      1. Create CDI 1.1 project with discovery mode annotated 2. Create two java classes (ie Bean1 and Bean2) 3. add scope to Bean1 and inject Bean2 ASSERT: warning is shown "No bean is eligible for injection to the injection point [JSR-299 §5.2.1] " 4. change discovery mode to all ASSERT: no warning is displayed in Bean1 FAIL: warning is still present. You have to edit Bean1 to reflect new discovery mode. NOTE: This applies for all beans - if you have more, you have to edit all of them (or run validate)
    • Workaround Exists
    • Hide

      run validate or edit bean

      Show
      run validate or edit bean

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

            Created:
            Updated:
            Resolved: