eclipse-ee4j / eclipse-ee4j/jersey
ValueFactoryProvider implementations parse relative to ContainerRequest instead of the Resource
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
ValueFactoryProvider implementations (MatrixParamValueFactoryProvider, PathParamValueFactoryProvider, QueryParamValueFactoryProvider and WebTargetValueFactoryProvider) look up the parameter values relative to getContainerRequest().getUriInfo() instead of relative to the associated Resource.
This blocks implementing #2444.
#### Affected Versions
[2.7]
Contributor guide
Research direction
Start by inspecting the MatrixParamValueFactoryProvider, PathParamValueFactoryProvider, QueryParamValueFactoryProvider, and WebTargetValueFactoryProvider implementations named in the issue. Compare their use of ContainerRequest.getUriInfo() with the associated Resource context, and verify that parameter values are resolved relative to the Resource as required for implementing #2444.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100