Author: buildbot
Date: Tue Feb 12 19:18:51 2013
New Revision: 850400
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-roadmap.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 Tue Feb 12 19:18:51
2013
@@ -277,16 +277,6 @@ And then we should use it in <tt>camel-i
<p>Maybe expose some interface having commit / rollback methods to make it
easier for component developers to implement custom logic. Currently they may
not know about <a shape="rect" href="oncompletion.html"
title="OnCompletion">OnCompletion</a> and how to use <tt>UnitOfWork</tt> on
Exchange to do this today.</p>
-<h4><a shape="rect"
name="Camel3.0-Ideas-Unifyuri%2Fref%28cmueller%29"></a>Unify uri/ref
(cmueller)</h4>
-<p>+1: claus, cmueller</p>
-
-<p>Instead of having both uri and ref for endpoints, we should unify this and
only use uri. If people want to use ref, then they can do that using "ref:xx"
as an uri. This would simplify code as we dont have to check for either one.</p>
-
-<h4><a shape="rect"
name="Camel3.0-Ideas-removethexxxRefoptions%28cmueller%29"></a>remove the
xxxRef options (cmueller)</h4>
-<p>+1: claus, cmueller</p>
-
-<p>In favor of the xxx option, we should remove the duplicated xxxRef options
from our components. This make our code and documentation more lean. We should
deprecate it as soon as possible and remove it in Camel 3.0.</p>
-
<h4><a shape="rect" name="Camel3.0-Ideas-RefactorUnitOfWork"></a>Refactor
UnitOfWork</h4>
<p>The implementation of DefaultUnitOfWork seems to have transformed itself
into a to broad concern where unit of work is doing a bit more work than the
transactional aspect that ties to its name.<br clear="none">
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 Tue Feb 12 19:18:51
2013
@@ -90,6 +90,18 @@
<h3><a shape="rect"
name="Camel3.0-Roadmap-Tasksforcamel3.0.0%28execute%29"></a>Tasks for
camel-3.0.0 (execute)</h3>
+<h4><a shape="rect"
name="Camel3.0-Roadmap-RemovethexxxRefoptionsfromourURI%28cmueller%29"></a>Remove
the xxxRef options from our URI (cmueller)</h4>
+
+<p>See <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL-6076";>CAMEL-6076</a></p>
+
+<p>In favor of the xxx options in our URI, we should remove the duplicated
xxxRef options from our components. This make our code and documentation more
lean. We should deprecate it as soon as possible and remove it in Camel 3.0.</p>
+
+<h4><a shape="rect"
name="Camel3.0-Roadmap-Unifyuri%2Frefinourendpoints%28cmueller%29"></a>Unify
uri/ref in our endpoints (cmueller)</h4>
+
+<p>See <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL-6077";>CAMEL-6077</a></p>
+
+<p>Instead of having both uri and ref for endpoints, we should unify this and
only use uri. If people want to use ref, then they can do that using "ref:xx"
as an uri. This would simplify code as we don't have to check for either
one.</p>
+
<h3><a shape="rect"
name="Camel3.0-Roadmap-Tasksforcamel3.x%28finalize%29"></a>Tasks for camel-3.x
(finalize)</h3></div>
</td>
<td valign="top">
