Jody Garnett ha scritto: > So a GeoTools.cleanup() then :-) > > Basically I would love to some how partition or set a checkpoint or > something and cleanup; and keep on going ... Ideally I would love to > do this on a Map by Map basis in uDig so when a Map is closed I can > "flush" out and geotools resources it was tracking. > > We *do* have the idea of a Transaction (basically keeping track of a > session) ... but so many things are done using "AUTO_COMMIT". Is > there any useful examples that do this sort of thing? I wish we could > do a "tag and sweep" and preserve things that are still in use...
That looks like a completely different use case than what I'm proposing. You can call it "add a cleanup method for developers that don't properly keep track of the resources they are handling". Which is a fine use case, would make the library easier to use. Just something different that what I'm trying to do here (donate back code for clean shutdown of web applications so that everybody can build a web app based on gt2 and have it undeploy cleanly). If the other geotools devs think that is not an interesting case I can just keep the patch in GeoServer and add the two/three extra manual cleanup methods I need in referencing. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
