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

[bu...@apache.org]

Author: buildbot
Date: Sat Mar 16 20:16:28 2013
New Revision: 854771

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-30-ideas.html
    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-ideas.html
==============================================================================
--- websites/production/camel/content/camel-30-ideas.html (original)
+++ websites/production/camel/content/camel-30-ideas.html Sat Mar 16 20:16:28 2013
@@ -241,11 +241,13 @@ This requires the TX manager supports su
 
 <h4><a shape="rect" name="Camel3.0-Ideas-Streamcaching"></a>Stream caching</h4>
 
-<p>We could add support for using <a shape="rect" href="hawtdb.html" title="HawtDB">HawtDB</a> as the persistent store for streams which overflow to disk store.</p>
+<p>We could add support for using <a shape="rect" href="hawtdb.html" title="HawtDB">HawtDB</a> as the persistent store for streams which overflow to disk store.<br clear="none">
+This might be implemented with the message store when it is used for stream caching.</p>
 
 <h4><a shape="rect" name="Camel3.0-Ideas-EIP"></a>EIP</h4>
 
-<p>The <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> EIP currently doesn't support persistence, we could introduce this and let it leverage <a shape="rect" href="hawtdb.html" title="HawtDB">HawtDB</a> such as we did with the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregator2</a> EIP.</p>
+<p>The <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> EIP currently doesn't support persistence, we could introduce this and let it leverage <a shape="rect" href="hawtdb.html" title="HawtDB">HawtDB</a> such as we did with the <a shape="rect" href="aggregator2.html" title="Aggregator2">Aggregator2</a> EIP.<br clear="none">
+This might be implemented with the message store when it is used for temporarily saving exchanes until they are in order.</p>
 
 <h4><a shape="rect" name="Camel3.0-Ideas-ScheduleinDSL"></a>Schedule in DSL</h4>
 

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 Sat Mar 16 20:16:28 2013
@@ -154,8 +154,8 @@ from(...)
 </span><span class="code-comment">// 2) Set body to <span class="code-keyword">null</span>.
 </span><span class="code-comment">// 3) Set Exchange.CLAIM_CHECK header to unique claim id.
 </span>from(...)
-   .claimCheck()  <span class="code-comment">// store body in <span class="code-keyword">default</span> store
-</span>   <span class="code-comment">// .claimCheck(header('bigHeader'), customStore) : store header in custom store 
+   .checkIn()  <span class="code-comment">// store body in <span class="code-keyword">default</span> store
+</span>   <span class="code-comment">// .checkIn(header('bigHeader'), customStore) : store header in custom store 
 </span>   .to(...);
 </pre>
 </div></div>
@@ -167,9 +167,9 @@ from(...)
 </span><span class="code-comment">// 3) Set body to the value fetched from the store.
 </span>from(...)
    <span class="code-comment">// .setHeader(Exchange.CLAIM_CHECK, <span class="code-keyword">const</span>(<span class="code-quote">"id"</span>)) : header should still contain the claim id 
-</span>   .claim() <span class="code-comment">// read body from <span class="code-keyword">default</span> store
-</span>   <span class="code-comment">// .transform(claim()) : more generically as expression
-</span>   <span class="code-comment">// .setHeader('bigHeader', claim(customStore)) : retrieve from custom store back into original header
+</span>   .reclaim() <span class="code-comment">// read body from <span class="code-keyword">default</span> store
+</span>   <span class="code-comment">// .reclaim().aggregationStrategy(myStrategy) : more generically using a aggregation strategy
+</span>   <span class="code-comment">// .reclaim(customStore).aggregationStrategy(myStrategy) : reclaim from custom store using a aggregation strategy
 </span>   .to(...);
 </pre>
 </div></div>