Raw Bean Types
- Dominant language
- Java
- Stars
- 240
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
The accepted test challenge https://github.com/jakartaee/cdi-tck/issues/429 has identified some ambiguity with how raw types in should be handled in bean definitions.
More discussion is required to determine:
- What, if any, portability is offered here from a CDI specification perspective
- What, if any, updates to the TCK need to occur
- What, if any, updates to the specification need to occur to reflect the outcome
The factor that lead to the test's exclusion is behavior flagged by the OpenJDK team as a bug ([JDK-8044366](https://bugs.openjdk.org/browse/JDK-8044366)). The bug identifies two options, direct and indirect, for determining the supertypes of a generic type. The author notes javac currently implements the indirect approach and advocates this is a bug and the correct approach is direct. This perspective is not yet accepted and the issue will not be resolved at the JDK level till other related issues are resolved.
Contributor guide
Research direction
Start by reviewing the accepted test challenge in jakartaee/cdi-tck#429 and the referenced OpenJDK bug JDK-8044366. Determine the portability position for raw types, then identify whether the TCK or CDI specification needs updates; done requires an agreed outcome and corresponding changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100