Gabriel Roldán wrote: > okay, I'm down to 3 failures: > - testDisjointFilter > So this one is actually serious? Do we have a plan ... or can we make a plan? > - testInsertGeometries and testConstructShapePolygon are due to a defect in > how polygons are mapped to the double[][][] the sde java api uses. > > All those are beasts I could overcome independently of the command queue > stuff, so I'll be working on the later now. > > What I want to do: > start moving stuff that needs SeConnection, SeLayer, etc to be executed by > Session.execute(Command) > May imply Session.createXYZ() should no longer be needed at the end of the day > Session has a few other useful methods; like for getting an existing table (and making use of a cache of SeTable associated with the connection). As such we may need to allow for: Command.execute( SeConnection, Session )?
So I agree we have two separate tasks ahead: - You can introduce command queue internally for each Session (now that we are completely isolated) - I can move the "metadata" methods; creating a FeatureType etc... over to ArcSDEDataStore.getConnection( Command ) , and then work on reusing a single Session in my ArcSDEMinimalDataStore subclass ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
