Justin Deoliveira ha scritto: >> Hi Justin, >> option one looks fine, but GeoServer heavily uses FeatureStore >> wrappers for a number of reasons, and the actual API uses FeatureStore >> as well, I can't remember a place where we use DataStore directly >> (there may be, I haven't checked). >> Given that most of the querying methods are in FetureSource anyways, I'd >> suggest to make the FeatureSources implement GmlObjectAware instead. > > You bring up a good point... I never thought about the wrappers we use > in GeoServer... I guess that would be mean that the creator of the > wrapper would have to check for the interface, and also create a wrapper > that implements it... kind of ugly. What do you think?
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). Yet, I don't see quick escape routes from this wrapping madness... Cheers Andrea ------------------------------------------------------------------------- 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
