camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r849509 - in /websites/production/camel/content: book-in-one-page.html cache/main.pageCache camel-30-ideas.html
Date Tue, 05 Feb 2013 18:23:56 GMT
Author: buildbot
Date: Tue Feb  5 18:23:55 2013
New Revision: 849509

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-30-ideas.html

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Tue Feb  5 18:23:55 2013
@@ -3210,11 +3210,10 @@ mock.allMessages().arrives().noLaterThan
 Override when using <a shape="rect" href="advicewith.html" title="AdviceWith">advice
with</a>&#160;and return true. &#160;This helps in knowing the adviceWith is
to be used, and the&#160;CamelContext&#160;will not be started before&#160;the
advice with takes place. This delay helps by ensuring the advice with has been property setup
before the&#160;CamelContext&#160;is started.
 <div class="panelMacro"><table class="infoMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/information.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Its
important to start the CamelContext manually from the unit test after you are done doing all
the advice with.</td></tr></table></div>
 <p><br clear="none" class="atl-forced-newline"> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"> Returns false. &#160;the CamelContext is started
automatically before test methods are invoked. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> boolean isCreateCamelContextPerClass() <br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1" class="confluenceTd">
See&#160;<a shape="rect" href="#BookInOnePage-SetupCamelContextonceperclass%2Corpereverytestmethod">Setup
CamelContext once per class, or per every test method</a>. </td><td colspan="1"
rowspan="1" class="confluenceTd"> The CamelContext and routes are recreated for each test
method. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
String isMockEndpoints() </td><td colspan="1" rowspan="1" class="confluenceTd">
Triggers the auto-mocking of endpoints whose URIs match the provided filter. &#160;The
default&#160;filter is null which disables this feature. &#160;Retur
 n "*" &#160;to match all endpoints. &#160;See&#160;org.apache.camel.impl.InterceptSendToMockEndpointStrategy&#160;for&#160;more
details on the registration of the mock endpoints. </td><td colspan="1" rowspan="1"
class="confluenceTd"> Disabled </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> boolean isUseDebugger() </td><td colspan="1" rowspan="1"
class="confluenceTd"> If this method returns true, the&#160;<b>debugBefore(Exchange
exchange, Processor processor, ProcessorDefinition&lt;?&gt; definition,&#160;String
id, String label)</b>&#160;and&#160;<br clear="none" class="atl-forced-newline">
-<b>debugAfter(Exchange exchange, Processor processor, ProcessorDefinition&lt;?&gt;
definition,&#160;String id, String label, long timeTaken)</b>&#160;methods are
invoked for each processor in the registered routes. </td><td colspan="1" rowspan="1"
class="confluenceTd"> Disabled. &#160;The methods are not invoked during the test.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> int
getShutdownTimeout() </td><td colspan="1" rowspan="1" class="confluenceTd"> Returns
the number of seconds that Camel should wait for graceful shutdown. &#160;Useful for decreasing
test times when a message is still in flight at the end of the test. </td><td colspan="1"
rowspan="1" class="confluenceTd"> Returns 10 seconds. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> boolean useJmx() </td><td colspan="1"
rowspan="1" class="confluenceTd"> If JMX should be disabled on the CamelContext used in
the test. </td><td colspan="1" rowspan="1" class="confluenceTd"> JMX is disa
 bled. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
JndiRegistry createRegistry() <br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Provides a hook for adding objects into the
registry. &#160;Override this method to bind objects to the registry before test methods
are invoked. </td><td colspan="1" rowspan="1" class="confluenceTd"> An empty registry
is initialized. </td></tr></tbody></table>
+<b>debugAfter(Exchange exchange, Processor processor, ProcessorDefinition&lt;?&gt;
definition,&#160;String id, String label, long timeTaken)</b>&#160;methods are
invoked for each processor in the registered routes. </td><td colspan="1" rowspan="1"
class="confluenceTd"> Disabled. &#160;The methods are not invoked during the test.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> int
getShutdownTimeout() </td><td colspan="1" rowspan="1" class="confluenceTd"> Returns
the number of seconds that Camel should wait for graceful shutdown. &#160;Useful for decreasing
test times when a message is still in flight at the end of the test. </td><td colspan="1"
rowspan="1" class="confluenceTd"> Returns 10 seconds. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> boolean useJmx() </td><td colspan="1"
rowspan="1" class="confluenceTd"> If JMX should be disabled on the CamelContext used in
the test. </td><td colspan="1" rowspan="1" class="confluenceTd"> JMX is disa
 bled. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
JndiRegistry createRegistry() <br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Provides a hook for adding objects into the
registry. &#160;Override this method to bind objects to the registry before test methods
are invoked. </td><td colspan="1" rowspan="1" class="confluenceTd"> An empty registry
is initialized. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
useOverridePropertiesWithPropertiesComponent </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Camel 2.10:</b> Allows to add/override properties when <a shape="rect" href="using-propertyplaceholder.html"
title="Using PropertyPlaceholder">Using PropertyPlaceholder</a> in Camel. </td><td
colspan="1" rowspan="1" class="confluenceTd"> null </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> ignoreMissingLocationWithPropertiesComponent
</td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"> <b>Camel 2.10:</b> Allows to control if Camel should ignore
missing locations for properties. </td><td colspan="1" rowspan="1" class="confluenceTd">
null </td></tr></tbody></table>
 </div>
 
 
-
 <h3><a shape="rect" name="BookInOnePage-JNDI"></a>JNDI</h3>
 
 <p>Camel uses a <a shape="rect" href="registry.html" title="Registry">Registry</a>
to allow you to configure <a shape="rect" href="component.html" title="Component">Component</a>
or <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> instances
or <a shape="rect" href="bean-integration.html" title="Bean Integration">Beans used
in your routes</a>. If you are not using <a shape="rect" href="spring.html" title="Spring">Spring</a>
or <span class="error">[OSGi]</span> then <a shape="rect" href="jndi.html"
title="JNDI">JNDI</a> is used as the default registry implementation.</p>

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 18:23:55 2013
@@ -150,7 +150,7 @@ Though this may comes later in Camel 3.x
 
 <p>Currently cross cutting concerns such as error handlers, interceptors, onCompletion
etc. can be define anywhere in the route. We should tighten this up and only allow this to
be configured in the start of the route. This also ensures when end users use code assistance
in their route development, the IDE will not popup a big list which includes these cross cutting
concerns. See also next note. (ProcessorDefinition will therefore be trimmed)</p>
 
-<h4><a shape="rect" name="Camel3.0-Ideas-MessageHistoryEIP%2FMessageStore%28ChristianOhr%3F%29"></a>Message
History EIP/Message Store (Christian Ohr?)</h4>
+<h4><a shape="rect" name="Camel3.0-Ideas-MessageHistoryEIP%2FMessageStore%28ChristianOhr%29"></a>Message
History EIP/Message Store (Christian Ohr)</h4>
 
 <p>(+1: hadrian)<br clear="none">
 We should make this EIP easier to use for end users, but offering a better public API. And
also have a pluggable message store, with filters that can filter what should be stored. As
well pluggable marshallers so people can marshal data from Exchange into a format the message
store can store (BLOB, XML, JSon etc.).<br clear="none">
@@ -255,12 +255,12 @@ 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>
-<p>+1: claus</p>
+<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>
-<p>+1: claus</p>
+<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>
 



Mime
View raw message