Andrea Aime wrote: > Well, I'm more or less in the same boat for versioning: if the original > feature source is versioning, I have to create a versioning wrapper > (in my case VersioningFeatureSource extends FeatureSource). > Note the reason we have the FeatureSource / FeatureStore / FeatureLocking interfaces is becasue WFS is a service set up around a single kind of resource (ie Fetures). GMLObjectId operation does not fit with this program so I have no problem with it being left as part of the DataStore api.
Strictly speaking it belongs with transaction rollback as part of the cross datastore methods; originally these were part of the Registry interface. > Yet, I don't see quick escape routes from this wrapping madness... > Dynamic beans? Wrap the interfaces you care about and provide pass though on the rest. Jody ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
