jakartaee / jakartaee/persistence
Add a reference to the Platform Specification for Jakarta EE integration concerns
- Dominant language
- Java
- Stars
- 267
- Forks
- 78
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 13
Description
We currently have several references in the Jakarta Persistence specification regarding behaviors in:
- Jakarta EE deployments
- Jakarta EE containers
- Jakarta EE environments
- Jakarta Contexts and Dependency Injection (CDI)
The TCK tests for these behaviors are actually part of the Platform TCK, and this is where the normative requirements should be defined as well. For EE 11, the Jakarta Persistence team has discussed beginning a process of moving EE integration concerns into the Jakarta Platform specification(s). The initial first step for EE 11 will simply be to add text to the Jakarta Persistence specification along the lines of:
"
Any reference to behaviors or requirements in Jakarta EE containers, deployments or environments is normatively defined in the Jakarta Platform Specification and/or profiles. See the Jakarta Persistence sections and TCK tests in the Jakarta Platform specifications and TCKs. Future versions of the Jakarta Persistence specification will remove the requirements statements and simply reference the Jakarta Platform for integration requirements.
"
Contributor guide
Research direction
Start by reading the Jakarta Persistence specification sections that discuss Jakarta EE deployments, containers, environments, and CDI, then identify where the integration guidance should be referenced. Add the proposed Platform Specification reference text and verify that it clearly redirects normative integration requirements to the Jakarta Platform specifications and TCKs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100