Author: buildbot
Date: Sat Mar 16 18:16:26 2013
New Revision: 854762
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-30-ideas.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 18:16:26
2013
@@ -87,6 +87,13 @@
<p>This is a mindmap of ideas for improving Camel 3.0. Fell free to discuss
this on the Camel <a shape="rect" href="mailing-lists.html" title="Mailing
Lists">Mailing Lists</a> if you have other ideas or feedback.</p>
+<h3><a shape="rect" name="Camel3.0-Ideas-Tableofcontents"></a>Table of
contents</h3>
+
+<table class="sectionMacro" border="0" cellpadding="5" cellspacing="0"
width="100%"><tbody><tr><td colspan="1" rowspan="1" valign="top"
class="confluenceTd" width="20%">
+<div class="panel" style="border-width: 1px;"><div class="panelContent">
+<div>
+<ul><li><a shape="rect" href="#Camel3.0-Ideas-Camel3.0Ideas">Camel 3.0
Ideas</a></li><ul><li><a shape="rect"
href="#Camel3.0-Ideas-Tableofcontents">Table of contents</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-JDKsupport">JDK support</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-JDK8JavaDSL">JDK8 Java DSL</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-ClearerArchitectureofCamelCore">Clearer
Architecture of Camel Core</a></li><ul><li><a shape="rect"
href="#Camel3.0-Ideas-Splitcamelcoreintomultipleparts%28hadrian%29">Split
camel-core into multiple parts (hadrian)</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Avoidshadinggoogleconcurrentlinkedmapincamelcore">Avoid
shading google concurrent linked map in camel-core</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Definescopeandrulesforcamelcorepackages%28champion%3F%29">Define
scope and rules for camel-core packages ( <em>champion</em>?)</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-Moreflexibleroutesatrunt
ime%28claus%29">More flexible routes at runtime (claus)</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-Fixrouteswithmultipleinputs%28claus%29">Fix
routes with multiple inputs (claus)</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-RouteinitializationlogicforJavaDSLandXMLDSLs%28claus%29">Route
initialization logic for Java DSL and XML DSLs (claus)</a></li><li><a
shape="rect"
href="#Camel3.0-Ideas-AddOnException%2CInterceptor%2Cetc.toJAXBmodelforaCamelContextDefinition%28claus%29">Add
OnException, Interceptor, etc. to JAXB model for a CamelContextDefinition
(claus)</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Tightenuproutedefinitions%28claus%29">Tighten up route
definitions (claus)</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-MessageHistoryEIP%2FMessageStore%28ChristianOhr%29">Message
History EIP/Message Store (Christian Ohr)</a></li></ul><li><a shape="rect"
href="#Camel3.0-Ideas-DependencyUpgrades">Dependency Upgrades</a></li><li><a
shape="rect" href="#Camel3.
0-Ideas-JMXnaming">JMX naming</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Removenotusedcomponents">Remove not used
components</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-SplitcamelcxfintoWSandREST">Split camel-cxf into WS and
REST</a></li><li><a shape="rect" href="#Camel3.0-Ideas-Oldideas">Old
ideas</a></li><ul><li><a shape="rect"
href="#Camel3.0-Ideas-Supportforasynchronoustransactions">Support for
asynchronous transactions</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Streamcaching">Stream caching</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-EIP">EIP</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-ScheduleinDSL">Schedule in DSL</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-AdvancedScalasupport">Advanced Scala
support</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-MoreEIPsas@annotations">More EIPs as
@annotations</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Unifiedstatistics">Unified statistics</a></li><li><a
shape="rect" href="#Camel3.0-I
deas-SEDA%2FVMcomponentstoleverageasyncroutingengine">SEDA/VM components to
leverage async routing engine</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-camelosgitest">camel-osgi-test</a></li><li><a
shape="rect" href="#Camel3.0-Ideas-REST">REST</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-Moreloadtests%28cmueller%29">More load tests
(cmueller)</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-OSGienhancements">OSGi enhancements</a></li><li><a
shape="rect"
href="#Camel3.0-Ideas-Easiercommit%2Frollbackforcomponentdevelopers">Easier
commit/rollback for component developers</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-RefactorUnitOfWork">Refactor UnitOfWork</a></li><li><a
shape="rect"
href="#Camel3.0-Ideas-ImprovementstoThreadPoolProfileforthreadmanagement">Improvements
to ThreadPoolProfile for thread management</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-TightenuponException">Tighten up
onException</a></li><li><a shape="rect" href="#Camel3.0-Ideas-Addcomposit
eEIPtocomposeanumberofEIPsintoasingleEIP">Add composite EIP to compose a
number of EIPs into a single EIP</a></li><li><a shape="rect"
href="#Camel3.0-Ideas-RemoveSpringtransactiondependencyfromJMScomponent%28RemovedbecauseSJMSwillbenonspringversion%29">
</a><del>Remove Spring transaction dependency from JMS component</del>
(Removed because SJMS will be non-spring version)</li></ul></ul></ul></div>
+</div></div></td></tr></tbody></table>
<h3><a shape="rect" name="Camel3.0-Ideas-JDKsupport"></a>JDK support</h3>
@@ -169,14 +176,14 @@ At least stuff like Predicate, Expressio
<p>This has been moved to its own <a shape="rect"
href="camel-30-message-store.html" title="Camel 3.0 - Message Store">Wiki
page</a>.</p>
-<h4><a shape="rect" name="Camel3.0-Ideas-DependencyUpgrades"></a>Dependency
Upgrades</h4>
+<h3><a shape="rect" name="Camel3.0-Ideas-DependencyUpgrades"></a>Dependency
Upgrades</h3>
<p>We should upgrade Jetty to 8.x as minimum. And if possible support Jetty
9.x which is in the works.<br clear="none">
Currently we are stuck on 7.x due CXF / Karaf etc uses that old version, and
thus we have been good citizen to align and use same version.<br clear="none">
AMQ is also using older Jetty, but that is easier to upgrade as well.</p>
-<h4><a shape="rect" name="Camel3.0-Ideas-JMXnaming"></a>JMX naming</h4>
+<h3><a shape="rect" name="Camel3.0-Ideas-JMXnaming"></a>JMX naming</h3>
<p>(+1: cgeer)</p>
@@ -185,7 +192,7 @@ AMQ is also using older Jetty, but that
<p>We should consider improve on this.</p>
-<h4><a shape="rect" name="Camel3.0-Ideas-Removenotusedcomponents"></a>Remove
not used components</h4>
+<h3><a shape="rect" name="Camel3.0-Ideas-Removenotusedcomponents"></a>Remove
not used components</h3>
<p>We should consider removing</p>
<ul class="alternate"
type="square"><li>camel-bam</li><li>camel-msv</li><li>org.apache.camel.view
from came-core</li><li>dot maven generator</li><li>... (there could be other
stuff to remove)</li></ul>
@@ -197,20 +204,12 @@ The DOT generator is not up to date and
<p>The MSV component is never/rarely used, and is causing some issues for
cutting releases, due some weird maven issues / download of JARs etc. And the
codebase has basically been left unchanged for 5+ years now.</p>
-<h4><a shape="rect" name="Camel3.0-Ideas-SplitcamelcxfintoWSandREST"></a>Split
camel-cxf into WS and REST</h4>
+<h3><a shape="rect" name="Camel3.0-Ideas-SplitcamelcxfintoWSandREST"></a>Split
camel-cxf into WS and REST</h3>
-<p>The camel-cxf component has grown too fat and has too many dependencies.
People would like to use a light-weight RS. We have already taked on Camel @dev
about splitting camel-cxf into a WS and RS modules. As well refactor the
code-base as there is potential overlap with CXF itself and stuff to be
removed/trimmed/optimized etc. </p>
+<p>The camel-cxf component has grown too fat and has too many dependencies.
People would like to use a light-weight RS. We have already talked on Camel
@dev about splitting camel-cxf into a WS and RS modules. As well refactor the
code-base as there is potential overlap with CXF itself and stuff to be
removed/trimmed/optimized etc. </p>
<p>We can have a camel-cfx-core where we can have shared logic if that makes
sense.</p>
-
-<h4><a shape="rect"
name="Camel3.0-Ideas-RemoveSpringtransactiondependencyfromJMScomponent%28RemovedbecauseSJMSwillbenonspringversion%29"></a><del>Remove
Spring transaction dependency from JMS component</del> (Removed because SJMS
will be non-spring version)</h4>
-
-<p><del>(+1: cgeer)</del></p>
-
-<p><del>Refactor the JMS component to remove the dependency on Spring
PlatformTransactionManager and replace with JTA TransactionManager.</del></p>
-
-
<h3><a shape="rect" name="Camel3.0-Ideas-Oldideas"></a>Old ideas</h3>
<p><em>To be better defined and moved to the section above or removed</em></p>
@@ -333,7 +332,13 @@ It may make more sense to move onRedeliv
<h4><a shape="rect"
name="Camel3.0-Ideas-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>
+<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>
+
+<h4><a shape="rect"
name="Camel3.0-Ideas-RemoveSpringtransactiondependencyfromJMScomponent%28RemovedbecauseSJMSwillbenonspringversion%29"></a><del>Remove
Spring transaction dependency from JMS component</del> (Removed because SJMS
will be non-spring version)</h4>
+
+<p><del>(+1: cgeer)</del></p>
+
+<p><del>Refactor the JMS component to remove the dependency on Spring
PlatformTransactionManager and replace with JTA
TransactionManager.</del></p></div>
</td>
<td valign="top">
<div class="navigation">
