Unfortunately there are many other fault in the DataStore API... But I agree with you regarding the ones you detailed.
About the createSchema() you can call it with a null FeatureType and then catch if it throws an UnimplementedExcpetion or a NullPointerException, to le the Userr know it up-front. Anyway, at least in the JDBC world, the only DataStore that actually implements it, is the PostgisDataStore, and I'm adding it to the OracleDataStore. Remember, though, that the created tables won't have any primary key, because PKs simply doesn't exist in FeatureType/AttributeType. Bye Paolo Rizzi > -----Messaggio originale----- > Da: Jesse Eichar [mailto:[EMAIL PROTECTED] > Inviato: mercoledì 26 ottobre 2005 2.40 > A: [email protected] > Oggetto: [Geotools-devel] Feedback on DataStore API > > > I am using the DataStore api trying to make a pleasant user > experience > for creating featuretypes (and I'd like to remove and modify them at > some point in the future). As a result I have found a few > shortcomings > so far. > > 1. DataStore does not have events that notify listeners that a schema > has changed. This causes problems because I am forced to > more tightly > bind my code than I would like. An action that should know nothing > about the datastore viewer now has to tell the viewer to > refresh, which > is "silly". > 2. There is no way to query the DataStore as to whether the > createSchema > method can be used. This is a requirement for a good user > experience. > If a user goes to a bunch of work to create a new feature > type then at > the commit stage it backfires and says "sorry you can't add feature > types to this datastore" they are going to be choked. > 3. There is no way to remove FeatureTypes > 4. There is no way to modify FeatureTypes. > > For 3 and 4 GeoAPI has a reasonable approach but a few > comments come to > mind with regards to its API > 1. removeType takes a generic name rather than a > FeatureType. I like > the stronger typing of a FeatureType to identify which type > to remove. > 2. modifyType take a FeatureType as a parameter and I assume > that the > FeatureType that is being modified is located by matching the > TypeName. > I would like the original FeatureType to be a parameter as > well. This > allows the name of the FeatureType to be modified as well as > the attributes. > > Comments? > Jesse > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > AVVERTENZE AI SENSI DEL D. LGS. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i, sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceveste questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema; costituisce comportamento contrario ai principi dettati dal D. Lgs. 196/2003 il trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
