Yes I am finally working on ArcSDE again ... I have been asked to stop converting ArcSDEDataStore over to using a queue and instead look at a series of problems: - A connection leak from hitting "refresh" in uDig (arcsde connections are opened but not closed). My impression is that the render threads need to wait for ArcSDE to start returning results before "noticing" that they have been stopped, and then closing the ArcSDE connection. - The arcsde problem mentioned previously where an internal object id is accidentally being made available as an attribute; breaking any code that tries to "split" an existing feature into two...
As for testing I am still looking at 19 failures for the ArcSDE package, Gabriel / Saul if you have a different number I would be pleased to know. Cheers, Jody ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
