Author: buildbot
Date: Tue Sep 4 14:17:28 2012
New Revision: 831116
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-run-maven-goal.html
websites/production/camel/content/threading-model.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-run-maven-goal.html
==============================================================================
--- websites/production/camel/content/camel-run-maven-goal.html (original)
+++ websites/production/camel/content/camel-run-maven-goal.html Tue Sep 4
14:17:28 2012
@@ -138,6 +138,34 @@ OSGI-INF/blueprint/*.xml
<p>The <tt>applicationContextUri</tt> will currently load the file from the
classpath, so in the example above the myBlueprint.xml file must be in the root
of the classpath.</p>
+<h3><a shape="rect" name="CamelRunMavenGoal-RunningCDI"></a>Running CDI</h3>
+<p>From <b>Camel 2.11</b> onwards the <tt>camel:run</tt> plugin also supports
running a <a shape="rect" href="cdi.html" title="CDI">CDI</a> application</p>
+
+<p>You would need to configure the camel:run plugin to use CDI, by setting
useCDI to true as shown below</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-xml">
+ <span class="code-tag"><plugin></span>
+ <span class="code-tag"><groupId></span>org.apache.camel<span
class="code-tag"></groupId></span>
+ <span
class="code-tag"><artifactId></span>camel-maven-plugin<span
class="code-tag"></artifactId></span>
+ <span class="code-tag"><configuration></span>
+ <span class="code-tag"><useCDI></span>true<span
class="code-tag"></useCDI></span>
+ <span class="code-tag"></configuration></span>
+ <span class="code-tag"></plugin></span>
+</pre>
+</div></div>
+
+<p>This allows you to boot up any CDI services you wish - whether they are
Camel-related, or any other CDI enabled services.</p>
+
+<p>You should add the CDI container of your choice (e.g. Weld or OpenWebBeans)
to the dependencies of the camel-maven-plugin such as <a shape="rect"
class="external-link"
href="http://svn.apache.org/viewvc/camel/trunk/examples/camel-example-cdi/";>in
this example</a>.</p>
+
+<p>From the source of Camel you can run a CDI example via</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+cd examples/camel-example-cdi
+mvn compile camel:run
+</pre>
+</div></div>
+
<h3><a shape="rect" name="CamelRunMavenGoal-AboutDOTgeneration"></a>About DOT
generation</h3>
<p><tt>camel:run</tt> will by default try to run dot generation to generate <a
shape="rect" href="visualisation.html" title="Visualisation">Visualisation</a>
diagrams.<br clear="none">
This feature could in some rare cases cause the application to hang, so its by
default disabled in Camel 1.6.1 or newer.</p>
Modified: websites/production/camel/content/threading-model.html
==============================================================================
--- websites/production/camel/content/threading-model.html (original)
+++ websites/production/camel/content/threading-model.html Tue Sep 4 14:17:28
2012
@@ -170,6 +170,10 @@ See the <tt>org.apache.camel.spi.Executo
<h3><a shape="rect" name="ThreadingModel-Shutdown"></a>Shutdown</h3>
<p>All thread pools created by Camel will be properly shutdown when
<tt>CamelContext</tt> shutdowns which ensures no leaks in the pools in case you
run in a server environment with hot deployments and the likes.</p>
+<p>The <tt>ExecutorServiceManager</tt> has APIs for shutting down thread pools
graceful and aggressively. Its encourage to use this API for creating and
shutting down thread pools.</p>
+
+<p>From <b>Camel 2.10.2</b> onwards Camel the graceful
<tt>shutdown(executorService)</tt> method from <tt>ExecutorServiceManager</tt>
will shutdown graceful at first, until a timeout value is hit. After that it
shutdown aggressively. The timeout value is by default <tt>5000</tt> millis.
You can configure a custom value on the <tt>ExecutorServiceManager</tt> if
needed.</p>
+
<h3><a shape="rect" name="ThreadingModel-SeeAlso"></a>See Also</h3>
<ul class="alternate" type="square"><li><a shape="rect"
href="architecture.html" title="Architecture">Architecture</a></li><li><a
shape="rect" href="async.html" title="Async">Async</a></li></ul>
</div>
