svn commit: r914401 - in /websites/production/camel/content: blueprint-testing.html cache/main.pageCache

[bu...@apache.org]

Author: buildbot
Date: Mon Jun 30 06:17:54 2014
New Revision: 914401

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/blueprint-testing.html
    websites/production/camel/content/cache/main.pageCache

Modified: websites/production/camel/content/blueprint-testing.html
==============================================================================
--- websites/production/camel/content/blueprint-testing.html (original)
+++ websites/production/camel/content/blueprint-testing.html Mon Jun 30 06:17:54 2014
@@ -86,7 +86,13 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="BlueprintTesting-BlueprintTesting">Blueprint Testing</h2><p><strong>Available as of Camel 2.10</strong></p><p><a shape="rect" href="testing.html">Testing</a> is a crucial part of any development or integration work. Camel supports the definition of <a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint routes</a>, but given Blueprint is an OSGi specific technology, writing unit tests is quite difficult. This library leverages <a shape="rect" class="external-link" href="http://code.google.com/p/pojosr/" rel="nofollow">PojoSR</a> which provides a service registry without using a fully compliant OSGi container. This allows defining real unit tests (as opposed to integration tests using <a shape="rect" class="external-link" href="http://team.ops4j.org/wiki/display/paxexam/Pax+Exam" rel="nofollow">Pax Exam</a>. Please make sure all test jars in you class path are OSGi bundle.</p><div class="code panel pdl" style="border-width: 
 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="BlueprintTesting-BlueprintTesting">Blueprint Testing</h2><p><strong>Available as of Camel 2.10</strong></p>    <div class="aui-message hint shadowed information-macro">
+                            <span class="aui-icon icon-hint">Icon</span>
+                <div class="message-content">
+                            <p><strong>camel-test-blueprint</strong> does only support testing one CamelContext. So if you have 2 or more CamelContexts in your blueprint XML files, then first found CamelContext is used during testing.</p>
+                    </div>
+    </div>
+<p><a shape="rect" href="testing.html">Testing</a><span style="line-height: 1.4285715;"> is a crucial part of any development or integration work. Camel supports the definition of </span><a shape="rect" href="using-osgi-blueprint-with-camel.html">Blueprint routes</a><span style="line-height: 1.4285715;">, but given Blueprint is an OSGi specific technology, writing unit tests is quite difficult. This library leverages </span><a shape="rect" class="external-link" href="http://code.google.com/p/pojosr/" style="line-height: 1.4285715;" rel="nofollow">PojoSR</a><span style="line-height: 1.4285715;"> which provides a service registry without using a fully compliant OSGi container. This allows defining real unit tests (as opposed to integration tests using </span><a shape="rect" class="external-link" href="http://team.ops4j.org/wiki/display/paxexam/Pax+Exam" style="line-height: 1.4285715;" rel="nofollow">Pax Exam</a><span style="line-height: 1.4285715;">. Please make sure all test jars in 
 you class path are OSGi bundle.</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 // to use camel-test-blueprint, then extend the CamelBlueprintTestSupport class,
 // and add your unit tests methods as shown below.

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