Justin Deoliveira ha scritto: > 1. We either rename getBounds() to remove the conflict like we have been > doing for the other conflicts. > > 2. Or we get evil... and create a class in the api module which > satisfies two constraints: > > * It extends from JTS Enevleope > * It implements geoapi BoundingBox, and geoapi Envelope ( like > ReferencedEnvelope does now ) > > Then we change ReferencedEnvelope to extend our new Envelope and > everything should work as before.
Hem... I think I'm leaning towards 2 because it involves less API breakage for users (and for us too, since Envelope is quite a commonly used class). I know we're breaking things with other classes, but if we can keep the breakage low, it's a lot better (imho). Cheers Andrea ------------------------------------------------------------------------- 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
