Return-Path: 
 <commits-return-38042-apmail-camel-commits-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-commits-archive@www.apache.org
Delivered-To: apmail-camel-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C2299C720
	for <apmail-camel-commits-archive@www.apache.org>;
 Fri, 28 Nov 2014 17:20:35 +0000 (UTC)
Received: (qmail 99937 invoked by uid 500); 28 Nov 2014 17:20:35 -0000
Delivered-To: apmail-camel-commits-archive@camel.apache.org
Received: (qmail 99885 invoked by uid 500); 28 Nov 2014 17:20:35 -0000
Mailing-List: contact commits-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@camel.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@camel.apache.org>
List-Post: <mailto:commits@camel.apache.org>
List-Id: <commits.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list commits@camel.apache.org
Received: (qmail 99876 invoked by uid 99); 28 Nov 2014 17:20:35 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2014 17:20:35 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2014 17:20:07 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id BFD00238905A
	for <commits@camel.apache.org>; Fri, 28 Nov 2014 17:19:35 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: svn commit: r930892 - in /websites/production/camel/content:
 cache/main.pageCache camel-and-scr.html
Date: Fri, 28 Nov 2014 17:19:35 -0000
To: commits@camel.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20141128171935.BFD00238905A@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: buildbot
Date: Fri Nov 28 17:19:35 2014
New Revision: 930892

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-and-scr.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-and-scr.html
==============================================================================
--- websites/production/camel/content/camel-and-scr.html (original)
+++ websites/production/camel/content/camel-and-scr.html Fri Nov 28 17:19:35 2014
@@ -374,7 +374,7 @@ public class CamelScrExampleTest {
 </div></div><p>&#160;</p><p>Now, let's take a look at the interesting bits one by one.</p><p>&#160;</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Using property prefixing</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[        // Set property prefix for unit testing
         System.setProperty(CamelScrExample.PROPERTY_PREFIX, &quot;unit&quot;);]]></script>
-</div></div><p>This allows you to override parts of the configuration by prefixing properties with "unit.". For example, <code>unit.from</code> overrides <code>from</code> for the unit test.</p><p>Prefixes, as a whole, can be used to cover the differences between the runtime environments where your routes might run. Moving the unchanged bundle through development, testing and production environments is a typical use case.</p><p>&#160;</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Getting test configuration from annotations</b></div><div class="codeContent panelContent pdl">
+</div></div><p>This allows you to override parts of the configuration by prefixing properties with "unit.". For example, <code>unit.from</code> overrides <code>from</code> for the unit test.</p><p>Prefixes can be used to handle the differences between the runtime environments where your routes might run. Moving the unchanged bundle through development, testing and production environments is a typical use case.</p><p>&#160;</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Getting test configuration from annotations</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[        integration.prepare(null, ScrHelper.getScrProperties(integration.getClass().getName()));]]></script>
 </div></div><p>Here we configure the Service Component in test with the same properties that would be used in OSGi environment.</p><p>&#160;</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Mocking components for test</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[        // Fake a component for test
@@ -398,7 +398,7 @@ public class CamelScrExampleTest {
 </div></div><p>Here we start the Service Component and along with it the routes.</p><p>&#160;</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Sending a test message</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[        // Send the test message
         context.createProducerTemplate().sendBody(&quot;direct:start&quot;, &quot;hello&quot;);]]></script>
-</div></div><p>Here we send a message to a route in test.</p><h3 id="CamelandSCR-RunningthebundleinApacheKaraf">Running the bundle in Apache Karaf</h3><p>Once the bundle has been built with <code>mvn install</code> it's ready to be deployed.&#160;<span style="font-size: 14.0px;line-height: 1.4285715;">To deploy the project in Apache Karaf perform the following steps on Karaf command line:</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Deploying the bundle in Apache Karaf</b></div><div class="codeContent panelContent pdl">
+</div></div><p>Here we send a message to a route in test.</p><h3 id="CamelandSCR-RunningthebundleinApacheKaraf">Running the bundle in Apache Karaf</h3><p>Once the bundle has been built with <code>mvn install</code> it's ready to be deployed.&#160;<span style="font-size: 14.0px;line-height: 1.4285715;">To deploy the bundle on Apache Karaf perform the following steps on Karaf command line:</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Deploying the bundle in Apache Karaf</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[# Add Camel feature repository
 karaf@root&gt; features:chooseurl camel 2.15-SNAPSHOT
  
@@ -418,7 +418,7 @@ Press ctrl-c to stop watching the log.]]
 </div></div><h4 id="CamelandSCR-Overridingthedefaultconfiguration"><span style="font-size: 14.0px;line-height: 1.4285715;">Overriding the default configuration</span></h4><p>By default, Service Component's configuration PID equals the fully qualified name of its class. You can change the example bundle's properties with Karaf's&#160;<code>config:*</code> commands:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Override a property</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[# Override &#39;messageOk&#39; property
 karaf@root&gt; config:propset -p example.CamelScrExample messageOk &quot;This is better logging&quot;]]></script>
-</div></div><p>Or you can change the configuration directly by editing property files in Karaf's <code>etc</code> folder.</p><h4 id="CamelandSCR-UsingCamelSCRbundleasatemplate"><span style="font-size: 16.0px;line-height: 1.5625;">Using Camel SCR bundle as a template</span></h4><p>Let's say you have a Camel SCR bundle that implements an integration pattern that you use frequently, say, <strong>from &#8594;&#160;to</strong>, with success/failure logging and redelivery which also happens to be the pattern our example route implements. You probably don't want to create a separate bundle for every instance. No worries, SCR has you covered.</p><p>Create a configuration PID for your Service Component, but add a tail with a dash and SCR will use that configuration to create a new instance of your component.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a new Service Component instance</b></div>
 <div class="codeContent panelContent pdl">
+</div></div><p>Or you can change the configuration by editing property files in Karaf's <code>etc</code> folder.</p><h4 id="CamelandSCR-UsingCamelSCRbundleasatemplate"><span style="font-size: 16.0px;line-height: 1.5625;">Using Camel SCR bundle as a template</span></h4><p>Let's say you have a Camel SCR bundle that implements an integration pattern that you use frequently, say, <strong>from &#8594;&#160;to</strong>, with success/failure logging and redelivery which also happens to be the pattern our example route implements. You probably don't want to create a separate bundle for every instance. No worries, SCR has you covered.</p><p>Create a configuration PID for your Service Component, but add a tail with a dash and SCR will use that configuration to create a new instance of your component.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a new Service Component instance</b></div><div clas
 s="codeContent panelContent pdl">
 <script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[# Create a PID with a tail
 karaf@root&gt; config:edit example.CamelScrExample-anotherone