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

[spring-projects-issues]

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]

Juergen Hoeller commented

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

Juergen