jakartaee / jakartaee/platform
Remove Security Manager Dependency Across Platform
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
Since Jakarta EE 12 will likely support Java SE 21 and Java SE 25, it is necessary to remove any dependency on the Java SE Security Manager across the platform and all specifications. The Security Manager cannot be [enabled](https://inside.java/2024/12/11/quality-heads-up/) by Java SE 24. The thought is that in Java 29, SecurityManager APIs may not exist or may throw an error. It looks like some of this work was done in EE 11, but not all. As an example of pending work, see: https://github.com/jakartaee/cdi/issues/831.
Specification issues
- [ ] Connectors: https://github.com/jakartaee/connectors/issues/148
- [ ] Enterprise Beans: https://github.com/jakartaee/enterprise-beans/issues/163
API update issues
- [x] Activation ([issue](https://github.com/jakartaee/jaf-api/issues/125) and [PR](https://github.com/jakartaee/jaf-api/pull/169))
- [ ] Batch ([issue](https://github.com/jakartaee/batch/issues/215) and [PR](https://github.com/jakartaee/batch/pull/216))
- [x] CDI ([issue](https://github.com/jakartaee/cdi/issues/831) and [PR](https://github.com/jakartaee/cdi/pull/830))
- [x] JSON-P ([issue](https://github.com/jakartaee/jsonp-api/issues/403) and [PR](https://github.com/jakartaee/jsonp-api/pull/412))
- [x] Mail ([issue](https://github.com/jakartaee/mail-api/issues/744) and [PR](https://github.com/jakartaee/mail-api/pull/745))
- [x] Persistence ([issue](https://github.com/jakartaee/persistence/issues/666) and [PR](https://github.com/jakartaee/persistence/pull/664))
- [x] REST ([issue](https://github.com/jakartaee/rest/issues/1262) and [PR](https://github.com/jakartaee/rest/pull/1295))
- [x] Servlet ([issue](https://github.com/jakartaee/servlet/issues/789) and [PR](https://github.com/jakartaee/servlet/pull/790)) (just a javadoc update)
- [x] Validation ([issue](https://github.com/jakartaee/validation/issues/242) and [PR](https://github.com/jakartaee/validation/pull/243)) (changes could be done in a service release since 3.1 was new in EE 11)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the unchecked Connectors, Enterprise Beans, and Batch issues linked in the checklist, and compare them with the completed API update issues to identify the remaining Security Manager work. Done means the outstanding platform and specification dependencies are addressed across the listed areas; this issue provides no repository files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100