Jody Garnett ha scritto: > That is a strong argument for justin's combining for FeatureSource and > FeatureCollection. Right now when a wrapper is applied I need to > implement FeatureReader or Iterator wrapper; FeatureCollectionWrapper > etc... this tends to keep on exploding the further up you move the > wrapper.
Indeed, writing wrappers for the current datastore API is a royal pain. > Can FeatureStore wrapper be applied? Or is this limited to read-only. I don't see any reason to limit it to read only. I used FeatureSource in the examples just because it's the base class. Some wrappers will have the side effect of turning a FeatureStore into a FeatureSource (the app schema datastore does it afaik) but that's by no means the rule. The type renamer wrapper we have to day, for example, is fully read/write Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
