org.geotools.renderer.style
Class DynamicSymbolFactoryFinder

Object
  extended by DynamicSymbolFactoryFinder

public final class DynamicSymbolFactoryFinder
extends Object

Searches for all available ExternalGraphicFactory and MarkFactory implementations.

In addition to implementing this interface dynamic symbol handlers should have a services file:

The file should contain a single line which gives the full name of the implementing class.

Example:
org.geotools.data.jdbc.DBCPDataSourceFactory

Module:
modules/unsupported/h2 (gt-h2.jar)

Field Summary
protected static Logger LOGGER
          The logger for the filter module.
 
Method Summary
static Iterator<ExternalGraphicFactory> getExternalGraphicFactories()
          Finds all implementations of ExternalGraphicFactory which have registered using the services mechanism.
static Iterator<MarkFactory> getMarkFactories()
          Finds all implementations of MarkFactory which have registered using the services mechanism.
static void scanForPlugins()
          Scans for factory plug-ins on the application class path.
 
Methods inherited from class Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

LOGGER

protected static final Logger LOGGER
The logger for the filter module.

Method Detail

getMarkFactories

public static Iterator<MarkFactory> getMarkFactories()
Finds all implementations of MarkFactory which have registered using the services mechanism.

Returns:
An iterator over all discovered datastores which have registered factories, and whose available method returns true.

getExternalGraphicFactories

public static Iterator<ExternalGraphicFactory> getExternalGraphicFactories()
Finds all implementations of ExternalGraphicFactory which have registered using the services mechanism.

Returns:
An iterator over all discovered datastores which have registered factories, and whose available method returns true.

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.



Copyright © 1996-2009 Geotools. All Rights Reserved.