svn commit: r851455 - in /websites/production/camel/content: cache/main.pageCache camel-30-message-store.html

[bu...@apache.org]

Author: buildbot
Date: Thu Feb 21 23:20:53 2013
New Revision: 851455

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 Thu Feb 21 23:20:53 2013
@@ -100,7 +100,7 @@ Implementations would handle the mapping
 <div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Work in progress</b><br clear="none">Feel free to add, edit, comment.... At some time we probably need to assign priorities as to what is indispensable for Camel 3.0 and what could be delivered in a later patch release</td></tr></table></div>
 
 <ul><li>Generically, entries in a Message Store can be created, updated, read and deleted.</li><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><li>Claim check <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>
+	<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><li>Claim check</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><li>Destination for the Tracer</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 part of an exchange should be stored (e.g. what exchange properties and message headers) and in which format (e.g. object serialization, JSON, using encryption)</li><li>Possibility to provide a filter condition to determine which exchanges should be stored (e.g. only failed exchanges, only with a certain message header)</li><li>Polling Consumer to randomly access a message store</li><li>Producer to write an exchange into a message store</li></ul>
@@ -126,6 +126,8 @@ from(...)
 </pre>
 </div></div>
 
+<h5><a shape="rect" name="Camel3.0-MessageStore-Claimcheck"></a>Claim check</h5>
+
 <div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;"><b>Setting default message store for route</b></div><div class="codeContent panelContent">
 <pre class="code-java">
 defaultMessageStore(myStore);