You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2012/04/11 11:19:47 UTC
svn commit: r812326 - in /websites/production/camel/content:
blueprint-testing.html cache/main.pageCache fop.html
Author: buildbot
Date: Wed Apr 11 09:19:46 2012
New Revision: 812326
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/blueprint-testing.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/fop.html
Modified: websites/production/camel/content/blueprint-testing.html
==============================================================================
--- websites/production/camel/content/blueprint-testing.html (original)
+++ websites/production/camel/content/blueprint-testing.html Wed Apr 11 09:19:46 2012
@@ -76,11 +76,10 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2><a shape="rect" name="BlueprintTesting-BlueprintTesting"></a>Blueprint Testing</h2>
+<p><b>Available as of Camel 2.10</b></p>
<p><a shape="rect" href="testing.html" title="Testing">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" title="Using OSGi blueprint with Camel">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>.</p>
-<p>Here is an <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-blueprint/src/test/java/org/apache/camel/test/blueprint/DebugBlueprintTest.java">example using XML Config</a>.</p>
-
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java"><span class="code-comment">// to use camel-test-blueprint, then extend the CamelBlueprintTestSupport class,
</span><span class="code-comment">// and add your unit tests methods as shown below.
@@ -109,8 +108,10 @@
</pre>
</div></div>
-<p>Also notice the use of <b><tt>getBlueprintDescriptor</tt></b> to specify the location of the OSGi Blueprint XML file.</p>
+<p>Also notice the use of <b><tt>getBlueprintDescriptor</tt></b> to specify the location of the OSGi Blueprint XML file.<br clear="none">
+If you have multiple OSGi Blueprint XML files, then you can specify them separated by comma in the <b><tt>getBlueprintDescriptor</tt></b> method.</p>
+<p>And the Blueprint XML file. And link to the full file <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-blueprint/src/test/resources/org/apache/camel/test/blueprint/camelContext.xml">here</a></p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml"><blueprint xmlns=<span class="code-quote">"http://www.osgi.org/xmlns/blueprint/v1.0.0"</span>
<span class="code-keyword">xmlns:xsi</span>=<span class="code-quote">"http://www.w3.org/2001/XMLSchema-instance"</span>
@@ -133,15 +134,13 @@
</pre>
</div></div>
-<p>If you have multiple OSGi Blueprint XML files, then you can specify them separated by comma in the <b><tt>getBlueprintDescriptor</tt></b> method.</p>
-
<p>In order to define blueprint tests, you need to add the following dependency in your pom:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
<span class="code-tag"><dependency></span>
<span class="code-tag"><groupId></span>org.apache.camel<span class="code-tag"></groupId></span>
<span class="code-tag"><artifactId></span>camel-test-blueprint<span class="code-tag"></artifactId></span>
- <span class="code-tag"><version></span>2.10-SNAPSHOT<span class="code-tag"></version></span>
+ <span class="code-tag"><version></span>2.10<span class="code-tag"></version></span>
<span class="code-tag"><scope></span>test<span class="code-tag"></scope></span>
<span class="code-tag"></dependency></span>
</pre>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/fop.html
==============================================================================
--- websites/production/camel/content/fop.html (original)
+++ websites/production/camel/content/fop.html Wed Apr 11 09:19:46 2012
@@ -76,7 +76,7 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2><a shape="rect" name="FOP-FOPComponent"></a>FOP Component</h2>
-<p>*Available as of Camel 2.10</p>
+<p><b>Available as of Camel 2.10</b></p>
<p>The FOP component allows you to render a message into different output formats using <a shape="rect" class="external-link" href="http://xmlgraphics.apache.org/fop/index.html">Apache FOP</a>.</p>