Sorry I am under the assumtion here that CommonSuperClassThing is the templated DataStore ... - and that DataStore is a subclass with all the blanks filled in so that SimpleFeature / SimpleFeatureType client code does not break - ComplexDataStore is a similar thing with the blanks filled in for Feature / FeatureType access
While we could relax the constraint - publish a single class with Generics; force client code to guess / cast - I am not sure it buys us anything? > Why do we have to add new classes? The only reason I would see is for > convenience. I mean we just template datastore and the rest falls into > place. That only helps implementors; are we going to make a couple of methods in DataStoreFinder that search for the SimpleFeature/Feature case ... or ask client code to cast... Example: DataStore<SimpleFeature,SimpleFeatureType> shapefile = (DataStore<SimpleFeature,SimpleFeatureType>) DataStoreFinder.createDataStore( params ) Basically be as mean as you want to the implementors; what does this look like to the client code? Jody ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
