org.geotools.coverage
Class FactoryFinder

java.lang.Object
  org.geotools.coverage.FactoryFinder

public final class FactoryFinder

extends java.lang.Object

Defines static methods used to access the application's default factory implementation.

Since:

2.1

Version:

$Id: FactoryFinder.java 17672 2006-01-19 00:25:55Z desruisseaux $

Author:

Martin Desruisseaux

Method Summary

static java.util.Set	getGridCoverageFactories() Returns a set of all available implementations for the GridCoverageFactory.
static GridCoverageFactory	getGridCoverageFactory(Hints hints) Returns the first implementation of GridCoverageFactory matching the specified hints.
static void	scanForPlugins() Scans for factory plug-ins on the application class path.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Detail

getGridCoverageFactory

public static GridCoverageFactory getGridCoverageFactory(Hints hints)
                                                  throws FactoryRegistryException

Returns the first implementation of GridCoverageFactory matching the specified hints. If no implementation matches, a new one is created if possible or an exception is thrown otherwise.

Parameters:

hints - An optional map of hints, or if none.

Returns:

The first grid coverage factory that matches the supplied hints.

Throws:

FactoryRegistryException - if no implementation was found or can be created for the GridCoverageFactory interface.

getGridCoverageFactories

public static java.util.Set getGridCoverageFactories()

Returns a set of all available implementations for the GridCoverageFactory.

Returns:

Set of available grid coverage factory implementations.

scanForPlugins

public static void scanForPlugins()

Scans for factory plug-ins on the application class path. This method is needed because the application class path can theoretically change, or additional plug-ins may become available. Rather than re-scanning the classpath on every invocation of the API, the class path is scanned automatically only on the first invocation. Clients can call this method to prompt a re-scan. Thus this method need only be invoked by sophisticated applications which dynamically make new plug-ins available at runtime.