Author: buildbot
Date: Thu Feb 6 14:17:17 2014
New Revision: 896637
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 Thu Feb 6 14:17:17 2014
@@ -1 +1 @@
-1565224
+1565263
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 Thu Feb 6
14:17:17 2014
@@ -487,6 +487,7 @@ used for testing or experimenting.</p>
<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>
<li><strong>spi-fly-example-provider-consumer-bundle</strong> - a bundle that
is both a provider and a consumer at the same time. <a
href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-provider-consumer-bundle/";>source</a></li>
+<li><strong>spi-fly-example-resource-provider-bundle</strong> and
<strong>spi-fly-example-resource-client-bundle</strong> - these bundles show
that SPI Fly can be used to control the TCCL in OSGi for any situation, in this
case applied to resource loading via the TCCL. The provider bundle provides a
resource used by the Foo.doit() API. The client bundle contains Foo.doit() and
in there calls Thread.getContextClassLoader().getResource() to obtain the
resource. The TCCL has visibility of the provider bundle because both bundles
have the appropriate values set in the SPI-Provider and SPI-Consumer headers.
Source <a
href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-resource-provider-bundle/";>here</a>
and <a
href="http://svn.apache.org/repos/asf/aries/trunk/spi-fly/spi-fly-examples/spi-fly-example-resource-client-bundle/";>here</a>.</li>
</ul>
<h2 id="more-information">More Information</h2>
<p>More information can be found at the following resources:</p>
