camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r930918 - in /websites/production/camel/content: cache/main.pageCache camel-and-scr.html
Date Fri, 28 Nov 2014 21:19:07 GMT
Author: buildbot
Date: Fri Nov 28 21:19:07 2014
New Revision: 930918

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 21:19:07 2014
@@ -85,7 +85,13 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="CamelandSCR-WorkingwithCamelandSCR">Working
with Camel and SCR</h2><p><span style="font-size: 14.0px;line-height: 1.4285715;">SCR
stands for Service Component Runtime and is an implementation of OSGi Declarative Services
specification. SCR enables any plain old Java object to expose and use OSGi services with
no boilerplate code.</span></p><p>OSGi framework knows your object by looking
at SCR descriptor files in its bundle which are typically generated from Java annotations
by a plugin such as <code><a shape="rect" class="external-link" href="https://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin.html">org.apache.felix:maven-scr-plugin</a></code>.</p><p>Running
Camel in an SCR bundle is a great alternative for Spring DM and Blueprint based solutions
having significantly fewer lines of code between you and the OSGi framework. Using SCR your
bundle can remain completely in Java world; there is no need to edit XML 
 or properties files. This offers you full control over everything and means your IDE of choice
knows exactly what is going on in your project.</p><h3 id="CamelandSCR-CamelSCRsupport">Camel
SCR support</h3><p><strong>Available as of Camel 2.15.0</strong></p><p><span
style="line-height: 1.4285715;"><code>org.apache.camel/camel-scr</code> bundle
provides a base class, <code>AbstractCamelRunner</code>, which manages a Camel
context for you and a helper class, <code>ScrHelper</code>, for using your SCR
properties in unit tests. Camel-scr feature for Apache Karaf&#160;</span><span
style="line-height: 1.4285715;">defines all features and bundles required for running Camel
in SCR bundles.</span></p><p><code>AbstractCamelRunner</code>&#160;class
ties CamelContext's lifecycle to Service Component's lifecycle and handles configuration with
help of Camel's PropertiesComponent. All you have to do to make a Service Component out of
your java class is to extend it from <code>AbstractCamelRunner</c
 ode>&#160;and add the following <code><a shape="rect" class="external-link"
href="https://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html">org.apache.felix.scr.annotations</a></code>
on class level:</p><p>&#160;</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Add
required annotations</b></div><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="CamelandSCR-WorkingwithCamelandSCR">Working
with Camel and SCR</h2><p><span style="font-size: 14.0px;line-height: 1.4285715;">SCR
stands for Service Component Runtime and is an implementation of OSGi Declarative Services
specification. SCR enables any plain old Java object to expose and use OSGi services with
no boilerplate code.</span></p><p>OSGi framework knows your object by looking
at SCR descriptor files in its bundle which are typically generated from Java annotations
by a plugin such as <code><a shape="rect" class="external-link" href="https://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin.html">org.apache.felix:maven-scr-plugin</a></code>.</p><p>Running
Camel in an SCR bundle is a great alternative for Spring DM and Blueprint based solutions
having significantly fewer lines of code between you and the OSGi framework. Using SCR your
bundle can remain completely in Java world; there is no need to edit XML 
 or properties files. This offers you full control over everything and means your IDE of choice
knows exactly what is going on in your project.</p><h3 id="CamelandSCR-CamelSCRsupport">Camel
SCR support</h3><p><strong>Available as of Camel 2.15.0</strong></p><p>&#160;</p>
   <div class="aui-message hint shadowed information-macro">
+                            <span class="aui-icon icon-hint">Icon</span>
+                <div class="message-content">
+                            <p>Camel-scr bundle is not included in Apache Camel versions
prior 2.15.0, but the artifact itself can be used with any Camel version since 2.12.0. This
means you can use Camel SCR support in, for example, Red Hat JBoss Fuse 6.1.</p>
+                    </div>
+    </div>
+<p>&#160;</p><p><span style="line-height: 1.4285715;"><code>org.apache.camel/camel-scr</code>
bundle provides a base class, <code>AbstractCamelRunner</code>, which manages
a Camel context for you and a helper class, <code>ScrHelper</code>, for using
your SCR properties in unit tests. Camel-scr feature for Apache Karaf&#160;</span><span
style="line-height: 1.4285715;">defines all features and bundles required for running Camel
in SCR bundles.</span></p><p><code>AbstractCamelRunner</code>&#160;class
ties CamelContext's lifecycle to Service Component's lifecycle and handles configuration with
help of Camel's PropertiesComponent. All you have to do to make a Service Component out of
your java class is to extend it from <code>AbstractCamelRunner</code>&#160;and
add the following <code><a shape="rect" class="external-link" href="https://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html">org.apache.felix.scr.annotations</a></code>
on class level:
 </p><p>&#160;</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Add
required annotations</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[@Component
 @References({
     @Reference(name = &quot;camelComponent&quot;,referenceInterface = ComponentResolver.class,



Mime
View raw message