Author: buildbot
Date: Wed Oct 24 14:17:41 2012
New Revision: 836027
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-30-roadmap.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-30-roadmap.html
==============================================================================
--- websites/production/camel/content/camel-30-roadmap.html (original)
+++ websites/production/camel/content/camel-30-roadmap.html Wed Oct 24 14:17:41
2012
@@ -238,6 +238,8 @@ And then we should use it in <tt>camel-i
Maybe this implementation should be named ExchangeContext and we can introduce
a simpler UnitOfWork concept. This would also allow us to refactor the
SubUnitOfWork into a general parent/child unit of work concept.<br clear="none">
However this requires API changes and thus is best kept for Camel 3.0</p>
+<p>This is also needed by the refactor of the Message History EIP.</p>
+
<h4><a shape="rect"
name="Camel3.0-Roadmap-ImprovementstoThreadPoolProfileforthreadmanagement"></a>Improvements
to ThreadPoolProfile for thread management</h4>
<p>We could move <tt>ThreadPoolProfile</tt> from <tt>org.apache.camel.spi</tt>
to <tt>org.apache.camel</tt> and have it in the root package. </p>
@@ -273,7 +275,10 @@ It may make more sense to move onRedeliv
<h4><a shape="rect"
name="Camel3.0-Roadmap-AddcompositeEIPtocomposeanumberofEIPsintoasingleEIP"></a>Add
composite EIP to compose a number of EIPs into a single EIP</h4>
<p>It would be nice if we have a DSL to compose a number of child EIPs into a
single EIP itself. eg a bit like <pipeline>. This would allow people to
make it easier to group together a number of EIPs into a single "unit". This
allows for example the error handler to redeliver to the composite EIP instead
of at the point of failure within the group. There are use-cases where people
want to do that. And today the solution is to split this into a new route,
which you then disable error handler by setting it to no error handler. And
then call the route using the direct endpoint. So instead if you could do
<composite> ... stuff goes here </composite> then that would be
neater, as you dont have to split into multiple routes. I think there is an old
JIRA ticket created about this a long time ago.</p>
-</div>
+
+<h4><a shape="rect" name="Camel3.0-Roadmap-MessageHistoryEIP"></a>Message
History EIP</h4>
+
+<p>We should make this EIP easier to use for end users, but offering a better
public API. And also have a pluggable message store, which filters that can
filter what should be store. As well pluggable marshallers so people can
marshal data from Exchange into a format the message store can store (BLOB,
XML, JSon etc.).</p></div>
</td>
<td valign="top">
<div class="navigation">