spring-cloud / spring-cloud/spring-cloud-stream
Provide a way to customize the ObjectMapper used in AMCB
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
AbstractMessageChannelBinder uses a custom ObjectMapper. It has code to check if the application provides an ObjectMapper. However, since AMCB is in a binder child context, it doesn't see beans provided by the application, which is only available in the parent context. See this for more context. Consider a way for the applications to circumvent this limitation.
Contributor guide
No contributing guide indexed for this repository
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
Start with AbstractMessageChannelBinder.java, especially the ObjectMapper check around the linked code, and review the linked issue comment for the parent and binder child-context behavior. Determine a supported way for an application-provided ObjectMapper to be used despite that context boundary; done means the customization path is defined and works for application beans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100