This section describes the implementation plan for each release of Weld 2.0.0
CDI 1.1 EDR1 (Weld 2.0.0.Alpha1)
| Issue number | Implementation | TCK | Notes | |
|---|---|---|---|---|
| Interceptors | ||||
| CDI-2 | DONE | DONE | ||
| CDI-115 | Will be done once interceptors are reimplemented using JBoss Invocation | Depends on WELD-997 | ||
| Decorators | ||||
| CDI-28 | Fixed in WELD-1001 | DONE (depends on WELD-1021) | ||
| CDI-78 | DONE | 1.1.EDR1 part DONE (depends on WELD-1034) | CDI-78 reopened | |
| Passivation | ||||
| CDI-136 | DONE | DONE | ||
| CDI-141 | DONE | DONE | ||
| CDI-140 | DONE as part of CDI-141 | DONE as part of CDI-141 | ||
| CDI-153 | No impact on implementation | DONE as part of CDI-141 | ||
| Proxying | ||||
| CDI-159 | DONE | DONE Tests from weld suite adopted | ||
| CurrentInjectionPoint | ||||
| CDI-52 | DONE | 1.1.EDR1 part DONE | ||
| Events | ||||
| CDI-75 | Already implemented | DONE | Do TCK tests first, then verify impl | |
| CDI-36 | DONE | DONE | ||
| Container access | ||||
| CDI-14* | DONE | DONE | ||
| Injection | ||||
| CDI-92 | DONE Injection point type validation not implemented yet. (see notes) | 1.1.EDR1 part DONE Tests from weld suite adopted | The spec needs further clarification (CDI-92). | |
| CDI-145 | DONE | DONE | ||
| Bootstrap | ||||
| CDI-118* | DONE | DONE | Depends on AS7-1197 | |
| Extensions SPI | ||||
| CDI-70 | Already implemented | DONE | Do TCK tests first, then verify impl | |
| CDI-132 | Already implemented | 1.1.EDR1 part DONE |
| |
| CDI-33* | DONE | DONE Tests from weld suite adopted | CDI-191 | |
| CDI-50* | DONE | DONE Tests from weld suite adopted | ||
| CDI-95* | DONE | 1.1.EDR1 part DONE Tests from weld suite adopted | ||
| CDI-96* | DONE | 1.1.EDR1 part DONE Tests from weld suite adopted | ||
| CDI-97* | DONE | DONE | ||
| CDI-98* | DONE | DONE Tests from weld suite adopted | ||
| CDI-99* | DONE | 1.1.EDR1 part DONE | CDI-99 reopened | |
| CDI-105* | DONE | DONE as part of CDITCK-252 | do this after CDI-97 | |
| CDI-109 | DONE | Not testable - non-portable behavior | CDI-109 reopened | |
| CDI-116* | Duplicate of CDI-97 | |||
| CDI-127 | DONE | 1.1.EDR1 part DONE Tests from weld suite adopted | CDI-127 reopened | |
| Java EE integration | ||||
| CDI-86! | DONE | 1.1.EDR1 part DONE Tests from weld suite adopted | CDI-207, WELD-1042 , | |
| Servlet integration | ||||
| CDI-73! | DONE | DONE | ||
| CDI-80 | DONE | DONE Tests from weld suite adopted | CDI-206 | |
| CDI-102 | DONE | DONE | ||
| CDI-135 | DONE | DONE Tests from weld suite adopted | See WELD-919 for details |
- Issues marked with a * (e.g. CDI-116*) require API changes to Weld.
- Issues marked with a ! (e.g. CDI-86!) require container integration changes
Process
RI and TCK development need to proceed in step. In general, to support the TDD, the TCK tests for a particular topic will be developed slightly ahead of RI development. IOW once basic tests for an area have been added to the TCK, RI development should proceed. In this way the RI can utilise the TCK tests, and the TCK quickly gain confidence that the tests are correct.
In general a particular area will be completed before moving on to the next area.
The CDI EG is responsible for producing API artifacts, and, once available, the RI should be upgraded to use it. APIs which are not yet implemented should be stubbed out with an |UnsupportedOperationException| being thrown.
Resources
- Source code repository for 2.0 is located at https://github.com/weld/core/tree/2.0
- Weld project page is located at http://seamframework.org/Weld
- Source code repository for CDI TCK 1.1 is located at https://github.com/jboss/cdi-tck