camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r967624 - in /websites/production/camel/content: cache/main.pageCache camel-run-maven-goal.html
Date Sat, 03 Oct 2015 13:19:59 GMT
Author: buildbot
Date: Sat Oct  3 13:19:59 2015
New Revision: 967624

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-run-maven-goal.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 Sat Oct  3 13:19:59 2015
@@ -85,41 +85,18 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="CamelRunMavenGoal-camel:run">camel:run</h2>
-
-<p>The <strong>camel:run</strong> goal of the <a shape="rect" href="camel-maven-plugin.html">Camel
Maven Plugin</a> is used to run your Camel <a shape="rect" href="spring.html">Spring</a>
configurations in a forked JVM from Maven. A good example application to get you started is
the <a shape="rect" href="spring-example.html">Spring Example</a>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-cd examples/camel-example-spring
+<div class="wiki-content maincontent"><h2 id="CamelRunMavenGoal-camel:run">camel:run</h2><p>The
<strong>camel:run</strong> goal of the <a shape="rect" href="camel-maven-plugin.html">Camel
Maven Plugin</a> is used to run your Camel <a shape="rect" href="spring.html">Spring</a>
configurations in a forked JVM from Maven. A good example application to get you started is
the <a shape="rect" href="spring-example.html">Spring Example</a>.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd
examples/camel-example-spring
 mvn camel:run
 ]]></script>
-</div></div>
-
-<p>This makes it very easy to spin up and test your routing rules without having to
write a main(&#8230;) method; it also lets you create multiple jars to host different
sets of routing rules and easily test them independently.</p>
-
-<p>How this works is that the plugin will compile the source code in the maven project,
then boot up a Spring ApplicationContext using the XML confiuration files on the classpath
at</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-META-INF/spring/*.xml
-]]></script>
-</div></div>
-
-<p>If you want to boot up your Camel routes a little faster, you could try the <a
shape="rect" href="camel-embedded-maven-goal.html">camel:embedded</a> instead.</p>
-
-<h3 id="CamelRunMavenGoal-RunningOSGiBlueprint">Running OSGi Blueprint</h3>
-<p>From <strong>Camel 2.10</strong> onwards the <code>camel:run</code>
plugin also supports running a <a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint</a>
application, and by default it scans for OSGi blueprint files in</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-OSGI-INF/blueprint/*.xml
-]]></script>
-</div></div>
-
-<p>You would need to configure the camel:run plugin to use blueprint, by setting useBlueprint
to true as shown below</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-      &lt;plugin&gt;
+</div></div><p>This makes it very easy to spin up and test your routing
rules without having to write a main(&#8230;) method; it also lets you create multiple
jars to host different sets of routing rules and easily test them independently.</p><p>How
this works is that the plugin will compile the source code in the maven project, then boot
up a Spring ApplicationContext using the XML confiuration files on the classpath at</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[META-INF/spring/*.xml
+]]></script>
+</div></div><p>If you want to boot up your Camel routes a little faster,
you could try the <a shape="rect" href="camel-embedded-maven-goal.html">camel:embedded</a>
instead.</p><h3 id="CamelRunMavenGoal-RunningOSGiBlueprint">Running OSGi Blueprint</h3><p>From
<strong>Camel 2.10</strong> onwards the <code>camel:run</code> plugin
also supports running a <a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint</a>
application, and by default it scans for OSGi blueprint files in</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[OSGI-INF/blueprint/*.xml
+]]></script>
+</div></div><p>You would need to configure the camel:run plugin to use
blueprint, by setting useBlueprint to true as shown below</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
     &lt;plugin&gt;
         &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
         &lt;artifactId&gt;camel-maven-plugin&lt;/artifactId&gt;
         &lt;configuration&gt;
@@ -127,16 +104,8 @@ OSGI-INF/blueprint/*.xml
         &lt;/configuration&gt;
       &lt;/plugin&gt;    
 ]]></script>
-</div></div>
-
-<p>This allows you to boot up any Blueprint services you wish - whether they are Camel-related,
or any other Blueprint.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p
class="title">Using limited Blueprint container</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>We use the <a shape="rect" class="external-link" href="https://code.google.com/p/pojosr/"
rel="nofollow">PojoSR project</a> as the blueprint container. This project is not
a full fledged blueprint container. For that you can use <a shape="rect" class="external-link"
href="http://karaf.apache.org/">Apache Karaf</a> or <a shape="rect" class="external-link"
href="http://servicemix.apache.org/">Apache ServiceMix</a>.</p></div></div>
-
-<p>You can use the <code>applicationContextUri</code> configuration to
specify an explicit blueprint XML file, such as:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-      &lt;plugin&gt;
+</div></div><p>This allows you to boot up any Blueprint services you wish
- whether they are Camel-related, or any other Blueprint.</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Using limited Blueprint
container</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>We use the <a shape="rect" class="external-link"
href="https://code.google.com/p/pojosr/" rel="nofollow">PojoSR project</a> as the
blueprint container. This project is not a full fledged blueprint container. For that you
can use <a shape="rect" class="external-link" href="http://karaf.apache.org/">Apache
Karaf</a> or <a shape="rect" class="external-link" href="http://servicemix.apache.org/">Apache
ServiceMix</a>.</p></div></div><p>You can use the <code>applicationContextUri</code>
configuration to specify an explicit blueprint XML file, such as:</p><div class="code
panel 
 pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
     &lt;plugin&gt;
         &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
         &lt;artifactId&gt;camel-maven-plugin&lt;/artifactId&gt;
         &lt;configuration&gt;
@@ -148,19 +117,8 @@ OSGI-INF/blueprint/*.xml
         &lt;/configuration&gt;
       &lt;/plugin&gt;    
 ]]></script>
-</div></div>
-
-<p>The <code>applicationContextUri</code> 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.<br clear="none">
-The <code>configAdminPid</code> is the pid name which will be used as the pid
name for configuration admin service when loading the persistence properties file. <br
clear="none">
-The <code>configAdminFileName</code> is the file name which will be used to load
the configuration admin service properties file.</p>
-
-<h3 id="CamelRunMavenGoal-RunningCDI">Running CDI</h3>
-<p>From <strong>Camel 2.11</strong> onwards the <code>camel:run</code>
plugin also supports running a <a shape="rect" href="cdi.html">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 pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-      &lt;plugin&gt;
+</div></div><p>The <code>applicationContextUri</code> 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.<br clear="none"> The <code>configAdminPid</code>
is the pid name which will be used as the pid name for configuration admin service when loading
the persistence properties file. <br clear="none"> The <code>configAdminFileName</code>
is the file name which will be used to load the configuration admin service properties file.</p><h3
id="CamelRunMavenGoal-RunningCDI">Running CDI</h3><p>From <strong>Camel
2.11</strong> onwards the <code>camel:run</code> plugin also supports running
a <a shape="rect" href="cdi.html">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 pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
     &lt;plugin&gt;
         &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
         &lt;artifactId&gt;camel-maven-plugin&lt;/artifactId&gt;
         &lt;configuration&gt;
@@ -168,44 +126,12 @@ The <code>configAdminFileName</code> is
         &lt;/configuration&gt;
       &lt;/plugin&gt;    
 ]]></script>
-</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 pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-cd examples/camel-example-cdi
+</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 pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd
examples/camel-example-cdi
 mvn compile camel:run
 ]]></script>
-</div></div>
-
-<h3 id="CamelRunMavenGoal-AboutDOTgeneration">About DOT generation</h3>
-<p><code>camel:run</code> will by default try to run dot generation to
generate <a shape="rect" href="visualisation.html">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>
-
-<p>To enable it you should configure the <strong>useDot</strong> parameter:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-      &lt;plugin&gt;
-        &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
-        &lt;artifactId&gt;camel-maven-plugin&lt;/artifactId&gt;
-        &lt;configuration&gt;
-          &lt;useDot&gt;true&lt;/useDot&gt;
-        &lt;/configuration&gt;
-      &lt;/plugin&gt;    
-]]></script>
-</div></div>
-
-<h3 id="CamelRunMavenGoal-Loggingtheclasspath">Logging the classpath </h3>
-<p>From <strong>Camel 2.10</strong> onwards you can configure whether the
classpath should be logged when <code>camel:run</code> executes. In older releases
the classpath is always logged.<br clear="none">
-This can be verbose and noisy, so from Camel 2.10 onwards, the classpath is not logged anymore.
You can enable this in the configuration using:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-      &lt;plugin&gt;
+</div></div><h3 id="CamelRunMavenGoal-Loggingtheclasspath">Logging the
classpath</h3><p>From <strong>Camel 2.10</strong> onwards you can
configure whether the classpath should be logged when <code>camel:run</code> executes.
In older releases the classpath is always logged.<br clear="none"> This can be verbose
and noisy, so from Camel 2.10 onwards, the classpath is not logged anymore. You can enable
this in the configuration using:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
     &lt;plugin&gt;
         &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
         &lt;artifactId&gt;camel-maven-plugin&lt;/artifactId&gt;
         &lt;configuration&gt;



Mime
View raw message