After one full day hacking, I realized that the incompatible change proposal
("Make static ReferencingFactoryFinder methods non-static") was a source of
confusion. I have meet cases where I was unsure if I should use STRICT or
DEFAULT factory finders. I guess that users will not want to bother about this
choice.
I tried to fix GEOT-1659 in an other, more transparent, way. The API is not
modified - static methods remain statics. I though that making them non-static
would be good on a conceptual point of view, but given the difficulty to choose
the right instance I'm not so sure now.
There is one change for FactoryFinder implementors. I created a new class:
org.geotools.factory.FactoryFinder
which is the base class of ReferencingFactoryFinder, CoverageFactoryFinder,
GeometryFactoryFinder, JTSFactoryFinder and CommonFactoryFinder. The
GeoTools.addDefaultHints(Hints)
method moved to
FactoryFinder.mergeSystemHints(Hints)
Same semantic, with the addition of a little bit of internal mechanic for
handling StrictHints.
Commited on trunk as of revision 28974. Waiting for confirmation that it works
before to merge with the 2.4 branch.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
