The current geotools plug-in mechanism, FactorySPI limits environments
which use other plugin systems, such as GeoServer with spring, and udig
with eclipse.

So what the geotools team at foss came up with was that what is needed
is to be able to supply customs implementations of classes that locate
classes that implement a particular interface, based on a particular
environment.

Martin called it ServiceIteratorProvider. So essentially what we would
get is three implementations, one for factorySpi, one for spring, one
for eclipse.

The factoryFinder then delegates to all registered
ServiceIteratorProvider when it is called. So what applications must do
on startup is the following:

FactoryFinder.addServiceIterator( new SpringServiceIteratorProvider() )
in geoserver

FactoryFinder.addServiceIterator( new UdigServiceIteratorProvider() ) in
udig

FactorySPI will be registered by default to keep things backwards
compatible.

-Justin


-- 
Justin Deoliveira
[EMAIL PROTECTED]
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to