I am looking at the jts-wrapper implementation (currently dragged away from a branch) and seeing how it lines up with GeoAPI 2.1.next ... Some of the changes made are keeping me from compiling in a Java 1.4 environment - so we probably need to clean up our type erasing code.
Example: > C:\java\geotools\trunk\modules\unsupported\jts-wrapper\src\main\java\org\geotools\geometry\jts\spatialschema\geometry\pr > imitive\RingImpl.java:[55,7] getElements() in > org.geotools.geometry.jts.spatialschema.geometry.complex.ComplexImpl canno > t implement getElements() in > org.opengis.spatialschema.geometry.complex.Complex; attempting to use > incompatible return t > ype > found : java.util.Collection > required: java.util.Set Some of these classes that implement more then one GeoAPI interface can *never* be happy .. so we need to relax back to Collection for the type erased jar. Jody ------------------------------------------------------------------------- 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
