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

Java source reference search doesn't work for EL in CDI projects

    XMLWordPrintable

Details

    • Hide

      EXECUTE: Create a CDI project.
      EXECUTE: Add the following bean:

      @Named
      public class MyBean {
      
        @Produces @Named public String foo;
      
        @Produces @Named public String foo1() {
           return "";
        }
      
        public String foo2() {
           return "";
        }
      }
      

      And the following ELs to any page:

      #{myBean.foo2()}
      #{foo}
      #{foo1}
      

      ASSERT: Shift+Ctrl+G on MyBean should find #

      {myBean.foo2()}

      - FAILURE!
      ASSERT: Shift+Ctrl+G on MyBean.foo should find #

      {foo}

      - FAILURE!
      ASSERT: Shift+Ctrl+G on MyBean.foo1() should find #

      {foo1}

      - FAILURE!

      Show
      EXECUTE: Create a CDI project. EXECUTE: Add the following bean: @Named public class MyBean { @Produces @Named public String foo; @Produces @Named public String foo1() { return ""; } public String foo2() { return ""; } } And the following ELs to any page: #{myBean.foo2()} #{foo} #{foo1} ASSERT: Shift+Ctrl+G on MyBean should find # {myBean.foo2()} - FAILURE! ASSERT: Shift+Ctrl+G on MyBean.foo should find # {foo} - FAILURE! ASSERT: Shift+Ctrl+G on MyBean.foo1() should find # {foo1} - FAILURE!
    • Hide
      The Java source reference search facility did not work correctly for Expression Language within CDI projects. This consequently meant that users were unable to search within Expression Language elements. Correcting the issue has meant ensuring that the search participant works for any kind of Java project and delegates the search to Expression Language resolvers that will then search Expression Language elements. For the user this means that they are able to now perform a search using the Java source reference search facility and it will also search for their specified term within Expression Language elements.
      Show
      The Java source reference search facility did not work correctly for Expression Language within CDI projects. This consequently meant that users were unable to search within Expression Language elements. Correcting the issue has meant ensuring that the search participant works for any kind of Java project and delegates the search to Expression Language resolvers that will then search Expression Language elements. For the user this means that they are able to now perform a search using the Java source reference search facility and it will also search for their specified term within Expression Language elements.
    • Documented as Resolved Issue

    Description

      It seems that Shift+Ctrl+G on Java elements searches for EL only in Seam 2 projects and only if you are searching for a method/field reference (not a type).
      Our search participant should work for any kind of Java projects and delegates such a search to EL resolvers. So it's responsibility of EL resolvers to recognize if the element is used in the EL.

      Attachments

        Activity

          People

            dazarov_jira Daniel Azarov (Inactive)
            alexeykazakov Alexey Kazakov
            Isaac Rooskov Isaac Rooskov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: