>
> First off we need to hear back from other devs as this would be a core
> modification in a very core class, then we'll decide how to handle
> this. Anyways, the two most promising routes seem to suggest the
> usage of a DataStore wrapper (whether we need a factory or not, it's
> up to how the hooking is made).
> Also, if the datastore wrapper is made in GeoServer you can limit
> yourself to a handful of methods (no need to worry about the
> reader/writer methods DataStore provides, GeoServer does not use them),
> and throw unsupported operation exceptions for the others.
> Finally, yes, it's ok if the pre-generalized data is returned read-only.
An extension point seems reasonable to me. So what exactly would it look
like:
DataStoreWrapper {
boolean canHandle( FeatureTypeInfo featureType, DataStore dataStore );
DataStore wrap( FeatureTypeINfo featureType, DAtaSTore dataStore );
}
would we want to handle teh wrapping of FeatureSources as well? So
adding perhaps a:
FeatureSource wrap( FeatureTypeINfo featureTYpe, FeatureSource
featureSource );
Or is that overkill?
> Cheers
> Andrea
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
