aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r850971 - in /websites/staging/aries/trunk/content: ./ modules/spi-fly.html
Date Mon, 18 Feb 2013 14:34:36 GMT
Author: buildbot
Date: Mon Feb 18 14:34:36 2013
New Revision: 850971

Log:
Staging update by buildbot for aries

Modified:
    websites/staging/aries/trunk/content/   (props changed)
    websites/staging/aries/trunk/content/modules/spi-fly.html

Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 18 14:34:36 2013
@@ -1 +1 @@
-1447272
+1447281

Modified: websites/staging/aries/trunk/content/modules/spi-fly.html
==============================================================================
--- websites/staging/aries/trunk/content/modules/spi-fly.html (original)
+++ websites/staging/aries/trunk/content/modules/spi-fly.html Mon Feb 18 14:34:36 2013
@@ -457,13 +457,13 @@ id  State       Bundle
 used for testing or experimenting.</p>
 <p>The following modules can be found in this directory:</p>
 <ul>
-<li><strong>spi-fly-example-spi-bundle</strong> - a bundle providing an
SPI interface used by the other example bundles.</li>
-<li><strong>spi-fly-example-provider1-jar</strong> - a plain jar file providing
an implementation of the SPI (via <tt>META-INF/services</tt>).</li>
-<li><strong>spi-fly-example-provider1-bundle</strong> - a bundle that wraps
the jar file from the previous bullet and specifies it in its Bundle-ClassPath. This example
represents the common case where an existing SPI provider is wrapped as-is in an OSGi bundle.
This example uses the SPI Fly proprietary configuration.</li>
-<li><strong>spi-fly-example-provider2-bundle</strong> - a bundle that directly
provides an SPI service (via <tt>META-INF/services</tt>). This example uses OSGi
 specification compliant configuration.</li>
-<li><strong>spi-fly-example-client1-jar</strong> - a plain jar using java.util.ServiceLoader.load()
to obtain and invoke all services provided of a certain SPI.</li>
-<li><strong>spi-fly-example-client1-bundle</strong> - a bundle that wraps
the jar file from the previous bullet and lists it in its Bundle-ClassPath. This example represents
the common case where an existing SPI consumer is wrapped as-is in an OSGi bundle. This example
uses SPI Fly proprietary configuration.</li>
-<li><strong>spi-fly-example-client2-bundle</strong> - a bundle that has
code that invokes <tt>java.util.ServiceLoader.load()</tt> directly. This example
uses OSGi specification compliant configuration.</li>
+<li><strong>spi-fly-example-spi-bundle</strong> - a bundle providing an
SPI interface used by the other example bundles. <a href="http://search.maven.org/remotecontent?filepath=org/apache/aries/spifly/examples/org.apache.aries.spifly.examples.spi.bundle/1.0.0/org.apache.aries.spifly.examples.spi.bundle-1.0.0.jar">osgi-bundle</a>
<a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-spi-bundle/">source</a></li>
+<li><strong>spi-fly-example-provider1-jar</strong> - a plain jar file providing
an implementation of the SPI (via <tt>META-INF/services</tt>). <a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-provider1-jar/">source</a></li>
+<li><strong>spi-fly-example-provider1-bundle</strong> - a bundle that wraps
the jar file from the previous bullet and specifies it in its Bundle-ClassPath. This example
represents the common case where an existing SPI provider is wrapped as-is in an OSGi bundle.
This example uses the SPI Fly proprietary configuration. <a href="http://search.maven.org/remotecontent?filepath=org/apache/aries/spifly/examples/org.apache.aries.spifly.examples.provider1.bundle/1.0.0/org.apache.aries.spifly.examples.provider1.bundle-1.0.0.jar">osgi-bundle</a>
<a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-provider1-bundle/">source</a></li>
+<li><strong>spi-fly-example-provider2-bundle</strong> - a bundle that directly
provides an SPI service (via <tt>META-INF/services</tt>). This example uses OSGi
 specification compliant configuration. <a href="http://search.maven.org/remotecontent?filepath=org/apache/aries/spifly/examples/org.apache.aries.spifly.examples.provider2.bundle/1.0.0/org.apache.aries.spifly.examples.provider2.bundle-1.0.0.jar">osgi-bundle</a>
<a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-provider2-bundle/">source</a>
</li>
+<li><strong>spi-fly-example-client1-jar</strong> - a plain jar using java.util.ServiceLoader.load()
to obtain and invoke all services provided of a certain SPI. <a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-client1-jar/">source</a></li>
+<li><strong>spi-fly-example-client1-bundle</strong> - a bundle that wraps
the jar file from the previous bullet and lists it in its Bundle-ClassPath. This example represents
the common case where an existing SPI consumer is wrapped as-is in an OSGi bundle. This example
uses SPI Fly proprietary configuration. <a href="http://search.maven.org/remotecontent?filepath=org/apache/aries/spifly/examples/org.apache.aries.spifly.examples.client1.bundle/1.0.0/org.apache.aries.spifly.examples.client1.bundle-1.0.0.jar">osgi-bundle</a>
<a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-client1-bundle/">source</a></li>
+<li><strong>spi-fly-example-client2-bundle</strong> - a bundle that has
code that invokes <tt>java.util.ServiceLoader.load()</tt> directly. This example
uses OSGi specification compliant configuration. <a href="http://search.maven.org/remotecontent?filepath=org/apache/aries/spifly/examples/org.apache.aries.spifly.examples.client2.bundle/1.0.0/org.apache.aries.spifly.examples.client2.bundle-1.0.0.jar">osgi-bundle</a>
<a href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-client2-bundle/">source</a></li>
 </ul></div>
             <!-- Content -->
           </td>



Mime
View raw message