Justin Deoliveira wrote: > 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"? > I was thinking you may want to "assume" the FeatureID subclass of Identifier this week when doing the GeoAPI type erasing. Although I bet it only shows up as a Set<Identifier> anyways... Tell you what I will go start in on using Filter w/ Pojo so we can try an implementation of ObjectId as well.
Near as I can tell to "teach" geotools about new content we need: - an Identifier implementation for the content - a XPath implementation for the content (even if limited) Cheers, Jody ------------------------------------------------------------------------- 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
