[CONF] Apache Camel > Camel 3.0 - Message Store

[confluence]

Camel 3.0 - Message Store Page edited by Christian Ohr Changes (2) {note:title=Work in progress} The page intends to collect all ideas and proposals around the idea of a Message Store as a architectural concept in Camel. No implementation has started yet. You can participate by sharing your input here or post it to the dev mailing list. {note} For the initial brainstorming on the dev mailiing list, please check [this thread|http://camel.465427.n5.nabble.com/DISCUSS-Message-Store-td5721454.html]. h4. From the Camel 3.0 ideas page ... Full Content Work in progress The page intends to collect all ideas and proposals around the idea of a Message Store as a architectural concept in Camel. No implementation has started yet. You can participate by sharing your input here or post it to the dev mailing list. For the initial brainstorming on the dev mailing list, please check this thread. From the Camel 3.0 ideas page (+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). Change Notification Preferences View Online | View Changes | Add Comment