Jody Garnett a écrit :
> So here is what we need to do:
> - We need to make sure all the FactoryFinders use the same FactoryRegistry
If global 'addFactoryIterator' is the only rational, a singleton
FactoryRegistry
is one possible approach but is not required. The list of FactoryIterator don't
need to be a field of FactoryRegistry.
I started code for that. Will try to commit when I will have a chance (I was
away today).
> The class that should be called "RegistryFactoryFinder" is really only
> for the registry module:
> - It is not aimed for users! (It is for the registry module's own use)
> - If a module like unsupported/geometry needed to create content it
> should make its own GeometryFactoryFinder that gathers together the
> resources it needs (reuse of FactoryFinders is bad)
What is RegistryFactoryFinder?
If we are talking about CommonFactoryFinder or referencing.FactoryFinder, then
this is currently quite the opposite: they are intented for users, not module
maintainers. FactoryRegistry is the internal class to hide to users.
referencing.FactoryFinder (for example) is not about dependencies required for
internal org.geotools.referencing (I realize that I said that in yesterday IRC,
but it was not my mind). referencing.FactoryFinder is about exposing
org.geotools.referencing implementation to users.
Martin
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
