Jody Garnett wrote: > To be clear, both GeoTools and GeoAPI assumed strings would make good > identifiers. > The filter specification: > a) strongly types identifier (FeatureId, GMLObjectId, RecordId, ...) > b) allows for non String, or compound identifiers (ID and VERSION anyone?) > > Justin for your first cut do you want to just use FeatureId at the Java > 1.4 level? I will need > to relax that for an ObjectId next week, but it would let the compiler > help you this week. > Not sure what you mean by "using FeatureId at the Java 1.4 level" ?
> Jody >> Hi all, >> >> Issue with the new geoapi identifier stuff with regard to getting >> geotools on board with it. >> >> Right now, the geotools filter implementations implement the geoapi >> interfaces. The semantics of FeatureId have changed, so the geotools >> FidFilter interface needs to implement Id now, instead of FeatureId. >> >> However the change involves moving Set<String> getIDs() to >> Set<Identifier> getIDs(). And since our java 4 world is untyped, it is >> going to be hard to flush out all of the uses and change them over. Same >> goes for GeoServer ( even more so ). >> >> So what I propose is that we rename getIDs() to getIdentifiers(). I >> would rather know where things break now at compile time, then deal with >> ClassCastExceptions later at runtime. >> >> -Justin >> >> >> > > > !DSPAM:1004,45478f9642821527717022! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
