From: Jody G. <jga...@re...> - 2008-05-21 04:51:20
|
Gabriel I ended up modifying your Session contact with the taskExecutor; I needed to store Thread being used so I could detect command recursion. Cheers, Jody > Hi Gabriel; I see you put the command queue in - nice work. > > I have broken out the Transaction.State use into two: > - ArcTransactionState has the feature event notification and versioned > flag and is stored against the DataStore > - SessionTransactionState holds the Session and is stored against the > connectionPool > > ArcSDEConnectionPool has the following methods: > - getSession(); used to lease a Session from the pool > - getSession( Transaction ); used to access the Session for the provided > Transaction > - issueReadOnlyCommand( Command ) > > The last method is why I signed up for this work; the > ArcSDEConnectionReference subclass of ConnectionPool remembers the > single Session in use and will use it to issue read-only commands. If > you can review; I have changed a single bit of functionality over to use > issueReadOnlyCommand; the ArcSDEAdapter.fetSchema method can serve as an > example of what needs to be done. > > Jody > > ------------------------------------------------------------------------- > 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 > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geotools-devel > |