I would like that Geotools 2.4 branch contains the old EPSG factory
implementation with class renamed, but without the work on the way.
Rational:
* Current work on EPSG-factory seems to consist in a lot of copy
and paste in every directions (referencing Pair inner class
copied in metadata module, lot of very similar code copied
in AbstractCachedAuthorityFactory, CachedAuthorityDecorator,
AbstractAuthorityMediator). I contest the utility of some of
those classes. I will need some time for reviewing and surely
refactor this EPSG-factory work once it will be finished, so
it may not fit in the 2.4 time frame.
* If we commit only class renaming on Geotools 2.4, we will be
free to delete the deprecated classes for the work on trunk.
It will help to have a clearer picture for the EPSG-factory
work, which seems quite important for me given the amont of
code currently moving around in all those new classes.
* Once the EPSG-factory work will be finished (including reviewing),
we will need to wait a while in order to spot eventual problems.
It is too late to rush such a big change in the 2.4 framework,
unless we report 2.4 branching for at least 2 months.
* This EPSG-factory work would benefit a lot from Java 5 and its
java.util.concurrent package. EDU.oswego.cs.dl.util.concurrent
(currently used as a temporary workaround for our J2SE 1.4
restriction) is not the same: different API, different handling
of exception...
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
