Support passing the properties in the outbound filter/interceptor chain
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 400
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
Can be postponed and moved to ice-box, if preferred.
The particular case we have is passing a property from WriterInterceptor (or ContainerResponseFilter) to MessageBodyWriter, this will work with the implementation specific code, but preferably one would just do containerResponseContext.getProperties().put("a", "b").
Note at the moment MessageBodyWriter can not get such properties in the portable way, but the feature may be handy even at the filter and write interceptor level only
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 outbound filter/interceptor chain involving WriterInterceptor, ContainerResponseFilter, ContainerResponseContext, and MessageBodyWriter. Clarify whether properties must be portable through to MessageBodyWriter or only between filters and write interceptors, then define the API behavior and tests that demonstrate property visibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100