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

Support Mutable Messages with optional ID and timestamp headers [SPR-11468] #16094

Closed
spring-projects-issues opened this issue Feb 22, 2014 · 1 comment
Assignees
Labels
in: messaging type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Feb 22, 2014

Gary Russell opened SPR-11468 and commented

High volume data ingestion in Spring Integration requires a mutable message (so messages can be reused, avoiding garbage collection).

Also, it will be beneficial if the creation of ID and timestamp headers can be made optional.

To support the Spring Integration MutableMessage we require some loosening of constraints on the MessageHeaders object; specifically:

  • Remove final modifier on class
  • Add a protected no-arg constructor
  • Add a protected getter for the headers field (e.g. getRawHeaders()

Affects: 4.0.2

Issue Links:

  • INT-3309 Add MessageBuilderFactory Strategy
  • #16276 NPE in AbstractMessageSendingTemplate when headers are null and converter returns null
  • #19827 MessageHeaderAccessor's MutableMessageHeaders should be serializable

Referenced from: pull request #509

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Mar 28, 2014

Juergen Hoeller commented

Gary, since SPR master is dedicated to 4.1 now, feel free to apply those changes right away...

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants