svn commit: r1013149 - in /websites/staging/aries/trunk/content: ./ modules/containers.html

[buildbot]

Author: buildbot
Date: Tue May 30 11:11:53 2017
New Revision: 1013149

Log:
Staging update by buildbot for aries

Modified:
    websites/staging/aries/trunk/content/   (props changed)
    websites/staging/aries/trunk/content/modules/containers.html

Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 30 11:11:53 2017
@@ -1 +1 @@
-1796832
+1796833

Modified: websites/staging/aries/trunk/content/modules/containers.html
==============================================================================
--- websites/staging/aries/trunk/content/modules/containers.html (original)
+++ websites/staging/aries/trunk/content/modules/containers.html Tue May 30 
11:11:53 2017
@@ -348,7 +348,7 @@ protected void doGet(HttpServletRequest
 <p>In short - an OSGi Declarative Service Component is registered as a HTTP 
Whiteboard Servet. The Aries Containers Service Manager is
 injected into the <code>serviceManager</code> field and then used in the 
servlet to manage the deployment.</p>
 <p>TODO: Describe how to run the servlet using a small Felix setup.</p>
-<p><img alt="screenshot" src="osgidemo.png" /></p>
+<p><img alt="screenshot" src="containers/osgidemo.png" /></p>
 <h2 id="plain-java-example">Plain Java example<a class="headerlink" 
href="#plain-java-example" title="Permanent link">&para;</a></h2>
 <p>This example launches a small Java Application to create a service 
deployment. Initially a single container is deployed. The user can 
 modify the number of replicas using the application.</p>