Hi all, I am emailing the list hoping to get some feedback for an idea that i have. First a bit of context. I am working on the wfs xlink implementation for OWS-5. One of the requirements is to be able to "xlink" geometries.
Now... i know the proper way to do this is with associations in the new feature model. But for various reasons i am not using the full capabilities of the new feature model. So i have restorted to using "userData" on attributes for storing things like xlink and gml identifiers. Which has worked pretty good so far. However... i am at a point where i need to create features that does not have geometries. Actually, they have geometries, except the geometry has to be "empty". I can not simply have a null object because i still need the geometry userData for strogin things like crs, gml identifier, etc... But i need to recognize it as a "null" or "empty" geometry. So... my thought is to create an interface called "NullGeometry" or something like that. That way in the encoder bindings i can do an instance of check and encode it as an "xlinked" geometry, and not a normal one. Any thoughts, comments, feedback? I am open to suggestions here. Thanks all, -Justin -- Justin Deoliveira The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
