Justin Deoliveira wrote: >> GeoServer did in fact make the transition gradually; but this >> arrangement did not work for GeoTools - we are left with a release of >> GeoTools 2.3 in which users complain every week about Filter not >> working (when they use the GeoAPI interfaces *only*). > Perhaps you are on a different mailing list than I. Heh; my turn to rant I guess .. checking now. You are correct the last one was from Yingqi Tang on 19/01/2007 :-) >> Well I was working on the "switch to GeoAPI interfaces as they are >> made available" idea; I am fine with client code dragging its heels - >> but not fine with GeoServer and uDig dragging their heels. GeoTools >> can move as slow as these two applications. > Well part of the problem is that sometimes working with geoapi is like > trying to hit a moving target. If the trunk on trunk policy in > geoserver and udig hold up then this should be more manageble. To that end I have finally caught up our procedures with what is needed for this: - http://docs.codehaus.org/display/GEOT/GeoTools+change+proposal
I even used this issue as an example for you. Jody ------------------------------------------------------------------------- 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
