You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aries.apache.org by bu...@apache.org on 2012/05/01 10:09:38 UTC
svn commit: r815250 - in /websites/staging/aries/trunk/content: ./
modules/spi-fly.html
Author: buildbot
Date: Tue May 1 08:09:38 2012
New Revision: 815250
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 Tue May 1 08:09:38 2012
@@ -1 +1 @@
-1332557
+1332559
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 Tue May 1 08:09:38 2012
@@ -383,7 +383,10 @@ java.util.ServiceLoader in that it can l
While SPI Fly knows about ServiceLoader and treats it specially, the ServiceRegistry
class currently does not have special treatment. It can still be made to work
but this requires the following header in the provider bundle:
-<tt>SPI-Provider: javax.imageio.spi.ServiceRegistry</tt></li>
+<tt>SPI-Provider: javax.imageio.spi.ServiceRegistry</tt> on the client
+side you can use <tt>SPI-Consumer: javax.imageio.spi.ServiceRegistry#lookupProviders(java.l
+ ang.Class) </tt>
+ or <tt>SPI-Consumer: javax.imageio.spi.ServiceRegistry#lookupProviders<tt></li>
</ul>
<h2 id="examples">Examples</h2>
<p>The <tt>spi-fly-examples</tt> directory contains a number of example bundles that can be