Author: buildbot
Date: Wed Nov 13 01:22:28 2013
New Revision: 886452
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 Wed Nov 13
01:22:28 2013
@@ -88,7 +88,7 @@
<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><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>. Please make sure all test jars in you class path are OSGi bundle.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><