Skip to content

CompositeMessageConverter should allow MessageConverters to use different ContentTypeResolvers [SPR-11462] #16088

@spring-projects-issues

Description

@spring-projects-issues

David Turanski opened SPR-11462 and commented

Currenly CompositeMessageConverter.setDefaultContentTypeResolver() propagates to component AbstractMessageConverters which overrides existing ContentTypeResolvers. This method could be removed altogether and simply delegate to the converter's resolver.


Affects: 4.0.2

Referenced from: commits 6016536, 0da1eef

Metadata

Metadata

Assignees

Labels

in: messagingIssues in messaging modules (jms, messaging)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions