Uploaded image for project: 'CDI Specification Issues'
  1. CDI Specification Issues
  2. CDI-389

Revert CDI-85

    XMLWordPrintable

Details

    Description

      Bullet 4 of section 5.2.4 should be reverted back from:

      the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable from
      the upper bound, if any, of the type variable, or

      to

      the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable to
      the upper bound, if any, of the type variable, or

      See discussion at http://lists.jboss.org/pipermail/cdi-dev/2013-July/004290.html

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. CDITCK-349 Incorrect assertion regarding assignabillity of parameterized types

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. CDI-386 Two examples in section 5.2.4 contradict the rules of the same section

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Clarification - A clarification needed to a specification based on community feedback CDI-85 Clarify use of "to" and "from" when refering to assignments in section 5.2.3

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              asabotdu@redhat.com Antoine Sabot-Durand (Inactive)
              marko.luksa@gmail.com Marko Luksa (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: