camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r851154 - in /websites/production/camel/content: cache/main.pageCache camel-30-message-store.html
Date Tue, 19 Feb 2013 14:18:53 GMT
Author: buildbot
Date: Tue Feb 19 14:18:53 2013
New Revision: 851154

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-30-message-store.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-30-message-store.html
==============================================================================
--- websites/production/camel/content/camel-30-message-store.html (original)
+++ websites/production/camel/content/camel-30-message-store.html Tue Feb 19 14:18:53 2013
@@ -84,7 +84,23 @@
 <p>(+1: hadrian, claus)<br clear="none">
 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.).<br clear="none">
 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.<br clear="none">
-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).</p></div>
+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).</p>
+
+<h3><a shape="rect" name="Camel3.0-MessageStore-Summary"></a>Summary</h3>
+
+<p>...</p>
+
+<h3><a shape="rect" name="Camel3.0-MessageStore-Listofproposedfeatures"></a>List
of proposed features</h3>
+
+<ul><li>Ability to temporarily store exchanges for the following EIPs:
+	<ul><li>Aggregator, Multicast, RecipientList, Splitter : alternative to AggregationRepository,
making it eventually obsolete</li><li>Streaming Resequencer (CAMEL-949)</li><li>Stream
Caching <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/help_16.gif"
height="16" width="16" alt="" border="0"></li></ul>
+	</li><li>Ability to store exchanges for a defined period of time
+	<ul><li>Idempotent Consumer</li><li>Dead Letter Queue (CAMEL-4575)</li></ul>
+	</li><li>Ability to permanently store exchanges (e.g. for audit trails)</li><li>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.</li><li>Flexibility to specify what should be
stored (e.g. what exchange- and message properties) and in which format (e.g. object serialization,
JSON)</li><li>Possibility to filter what exchanges should be stored (using a predicate)</li><li>Polling
Consumer to randomly access a message store</li></ul>
+
+
+
+<h3><a shape="rect" name="Camel3.0-MessageStore-Examples"></a>Examples</h3></div>
         </td>
         <td valign="top">
           <div class="navigation">



Mime
View raw message