Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MarshallingHttpMessageConverter should not require both marshaller and unmarshaller [SPR-5942] #10611

Closed
spring-projects-issues opened this issue Jul 20, 2009 · 1 comment
Assignees
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Kenny MacLeod opened SPR-5942 and commented

MarshallingHttpMessageConverter.afterPropertiesSet() asserts that both the marshaller and unmarshaller have been set. However, there are use cases for which only one of these two is required.

I suggest making this check when the marshaller or unmarshaller is first used, rather than at init time.


Affects: 3.0 M3

Referenced from: commits 307fb0a

@spring-projects-issues
Copy link
Collaborator Author

Arjen Poutsma commented

Fixed.

@spring-projects-issues spring-projects-issues added in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 M4 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants