Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4032

Failure to resolve method type variable when using class-level bounded wildcard generics

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.0.0.CR1
    • None
    • EE
    • None
    • Hide

      Produce a class file with similar structure:

      class Foo extends Bar<T extends Baz> {
      void doThings(T arg) { }
      }

      The index created for such file could contain description containing java.lang.Object as a method argument instead of Baz since type variable remains unresolved during indexing.

      Show
      Produce a class file with similar structure: class Foo extends Bar<T extends Baz> { void doThings(T arg) { } } The index created for such file could contain description containing java.lang.Object as a method argument instead of Baz since type variable remains unresolved during indexing.

      This is a regression from EAP 6.x that can result in deployments failing on EAP7 that used to work correctly on EAP6. If a method uses generics that have class level bounds, then annotations on that method will not be discovered correctly.

              jgreene@redhat.com Jason Greene
              fedor.gavrilov Fedor Gavrilov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: