jakartaee / jakartaee/platform
Replace ServiceLoader-like implementations lookups in Faces by ServiceLoader itself
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
Following specs in EE 9.1 implement ServiceLoader-like implementation lookup themselves:
- [ ] Jakarta Faces: https://github.com/eclipse-ee4j/faces-api/issues/801
- [x] Jakarta XML Binding: https://github.com/eclipse-ee4j/jaxb-api/issues/194
- [x] Jakarta SOAP: https://github.com/eclipse-ee4j/saaj-api/issues/100
In EE 10, they should use ServiceLoader directly
Contributor guide
Research direction
Start with the Jakarta Faces issue 801 and the EE 9.1 specifications referenced here. Compare the completed Jakarta XML Binding and Jakarta SOAP issues to understand the expected migration, then identify the Faces implementation lookup entry points. Done means Jakarta Faces uses ServiceLoader directly for EE 10.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100