Page History

...

(+1: hadrian, claus)
We should make this EIP easier to use for end users, but offering a better public API. And also have a pluggable message store, with filters that can filter what should be stored. As well pluggable marshallers so people can marshal data from Exchange into a format the message store can store (BLOB, XML, JSon etc.).
A Message Store could provide transparent persistence to various EIP patterns (or used directly). Implementations would handle the mapping to the underlying database or file system or NoSQL or memory or whatever.
Message Store implementations are already there in various places, using different approaches, like in Stream Caching (only file system), AggregationRepository or IdempotentRepository. A Message Store is requested for in other places like Reliable stream resequencing (CAMEL-949) or Persistent Dead Letter Queue (CAMEL-4575).

Summary

...

List of proposed features

• Ability to temporarily store exchanges for the following EIPs:
  • Aggregator, Multicast, RecipientList, Splitter : alternative to AggregationRepository, making it eventually obsolete
  • Streaming Resequencer (CAMEL-949)
  • Stream Caching
• Ability to store exchanges for a defined period of time
  • Idempotent Consumer
  • Dead Letter Queue (CAMEL-4575)
• Ability to permanently store exchanges (e.g. for audit trails)
• Provide a certain level of manual retry. That is to get the original message from the store and feed it back in the originating route.
• Flexibility to specify what should be stored (e.g. what exchange- and message properties) and in which format (e.g. object serialization, JSON)
• Possibility to filter what exchanges should be stored (using a predicate)
• Polling Consumer to randomly access a message store

Examples