eclipse-ee4j / eclipse-ee4j/soteria
[3.0] Use ServiceLoader discovery to discover the CallerDetailsResolver and ResourceAccessResolver.
Open
- Dominant language
- Java
- Stars
- 73
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
This is to port the changes from https://github.com/eclipse-ee4j/soteria/issues/327 to the 3.0 branch.
Contributor guide
Research direction
Start by reading the linked Soteria issue 327, then inspect the 3.0 branch for CallerDetailsResolver and ResourceAccessResolver discovery. Confirm the expected ServiceLoader behavior and any tests or entry points identified there; the work is done when both resolvers are discovered as specified for the 3.0 branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100