felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r981585 - in /websites/staging/felix/trunk/content: ./ documentation/subprojects/apache-felix-dependency-manager/tutorials/getting-started.html
Date Tue, 01 Mar 2016 23:14:28 GMT
Author: buildbot
Date: Tue Mar  1 23:14:28 2016
New Revision: 981585

Staging update by buildbot for felix

    websites/staging/felix/trunk/content/   (props changed)

Propchange: websites/staging/felix/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar  1 23:14:28 2016
@@ -1 +1 @@

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-dependency-manager/tutorials/getting-started.html
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-dependency-manager/tutorials/getting-started.html
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-dependency-manager/tutorials/getting-started.html
Tue Mar  1 23:14:28 2016
@@ -96,6 +96,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>When using the dependency manager, your bundle activator is a subclass of <code>DependencyActivatorBase</code>.
It needs to implement the <code>init</code> life cycle method and can optionally
also implement a <code>destroy</code> method. Both methods take two arguments:
<code>BundleContext</code> and <code>DependencyManager</code>. The
latter is your interface to the declarative API you can use to define your components and
 <p>The following paragraphs will show various examples that explain how to do this.
Subsequently, some more advanced scenarios will be covered that involve listening to dependency
and component state changes and interacting with the OSGi framework from within your component
 <p>To use the dependency manager, you should put the <code>org.apache.felix.dependencymanager.jar</code>
in your classpath while compiling and in your OSGi framework when running.</p>
+<p>Java 8 is required since the dependency manager R8 release.</p>
 <h2 id="registering-a-service">Registering a service<a class="headerlink" href="#registering-a-service"
title="Permanent link">&para;</a></h2>
 <p>The first example is about registering a service. We extend <code>DependencyActivatorBase</code>
and in the <code>init</code> method we use the reference to the <code>DependencyManager</code>
to create and add a component. For this component we subsequently set its service interface
and implementation. In this case the interface is the <code>Store</code> interface,
the second parameter, <code>null</code>, allows you to provide properties along
with the service registration. For the implementation, we only mention the <code>Class</code>
of the implementation, which means the dependency manager will lazily instantiate it. In this
case, there is not much point in doing that because the component has no dependencies, but
if it had, the instantiation would only happen when those dependencies were resolved.</p>
 <p>Notice that the dependency manager API uses method chaining to create a more or
less "fluent" API that, with proper indentation, is very easy to read.</p>
@@ -252,7 +253,7 @@ h2:hover > .headerlink, h3:hover > .head
 <span class="p">}</span>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1665812 by marrs on Wed, 11 Mar 2015 09:02:04 +0000
+        Rev. 1733187 by pderop on Tue, 1 Mar 2016 23:14:13 +0000
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

View raw message