Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2374

Add tests for component classes supporting injection

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 8.0.0.CR1
    • None
    • CDI / Weld, Test Suite
    • None

    Description

      Right now the test suite does not contain tests for component classes with "Standard" injection support level (see Table EE.5-1 and EE.5.24 Support for Dependency Injection). The problem is such tests are missing in Java EE CTS as well. Actually CDI TCK tests some basic injection scenarios (servlet, filter, etc.) but it does not cover everything. And the division of responsibilities for testing is work in progress (see also http://lists.jboss.org/pipermail/cdi-dev/2013-October/004345.html).

      Note that in Java EE 7 component classes must support the use of interceptors as well.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-2375 Servlet component classes do not support interceptors

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-2457 HttpUpgradeHandlerInjectionSupportTestCase fails on Windows

          • 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

          Task - Represents a small unit of work that is not end-user facing. WFLY-2362 Support CDI interception of all EE components

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              mkouba@redhat.com Martin Kouba
              mkouba@redhat.com Martin Kouba
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: