camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r849512 - in /websites/production/camel/content: cache/main.pageCache camel-30-ideas.html
Date Tue, 05 Feb 2013 19:18:43 GMT
Author: buildbot
Date: Tue Feb  5 19:18:43 2013
New Revision: 849512

Production update by buildbot for camel


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  5 19:18:43 2013
@@ -201,12 +201,6 @@ schedule().every(5).minute().pollFrom(<s
 <p>The DSL should support both cron and non cron based, eg <a shape="rect" href="quartz.html"
title="Quartz">Quartz</a>, <a shape="rect" href="spring.html" title="Spring">Spring</a>
(spring 3 has cron) and regular JDK timers.</p>
-<h3><a shape="rect" name="Camel3.0-Ideas-UptodateScalaDSL"></a>Up-to-date
Scala DSL</h3>
-<p><b>Done in Camel 2.11</b></p>
-<p>The Scala DSL is slightly out of date as we have improved the DSL a bit here and
there. We should check the gap and ensure the Scala is up-to-date.</p>
 <h4><a shape="rect" name="Camel3.0-Ideas-AdvancedScalasupport"></a>Advanced
Scala support</h4>
 <p>-1: claus</p>
@@ -254,32 +248,16 @@ 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"></a>Unify uri/ref</h4>
+<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"></a>remove
the xxxRef options</h4>
+<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-LessSpringdependencies"></a>Less
Spring dependencies</h4>
-<p><b>DONE in Camel 2.9</b></p>
-<p>In camel-core we use the Spring JMX annotations to more easily enlist our MBeans.
We should move that logic to camel-spring. And introduce a Camel specific annotations to replace
those. For example ActiveMQ does that. This allows us to use camel-core with JMX without any
spring JARs at all. End users can still use the Spring JMX annotations in their custom code
/ components. They just need camel-spring on the classpath.</p>
-<p>Likewise we should move the ResourceEndpoint from camel-spring to camel-core. This
ensures that resource loading on classpath works with Camel as we can leverage the ClassResolver.
For example OSGi blueprint does not work with the Spring ResourceEndpoint. Also this ensures
the components that uses ResourceEndpoint will no longer be dependent on Spring.</p>
-<p>Then we are down to have Spring JAR dependency in: camel-jms and camel-mail.</p>
-<h4><a shape="rect" name="Camel3.0-Ideas-IntroduceCamelJMXannotations"></a>Introduce
Camel JMX annotations</h4>
-<p><b>DONE in Camel 2.9</b></p>
-<p>See above about less Spring dependency.</p>
 <h4><a shape="rect" name="Camel3.0-Ideas-RefactorUnitOfWork"></a>Refactor
 <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">

View raw message