Hi All, This is a request for comments as I'm working on a WFS DataStore 1.1.0 capable. The short term goal is to have a read-only WFS 1.1.0 datastore that can be used on uDig. Less than two weeks from now.
So, by one side, the current WFS datastore is: - only 1.0.0 - fairly unmaintained, and quite hard to maintain imho. Yet received a lot of fixes from different contributors (Jesse, Jody, etc) By the other side, for 1.1.0 we want to leverage new parsing tech (gtxml), so it was tempting at first to simply start a new datastore. But we're shipping geoserver with the current one by default for WFS 1.0 support, and I think it would be a pity to end up with two under-maintained datastores. Still, time constraints won't allow for a full redesign of the current one, but I'd like to start the WFS 1.1 support on the same wfs plugin in order to establish the basis for an upgrade path in order to get both versions support on the same track, aiming at lowering maintenance costs. I also intend to do some tracing bullets approach as in the end it needs to work in udig so I'd be constantly verifying I don't break 1.0 support in udig while 1.1 support advances smoothly. If this seems ok, it'd imply moving some stuff around on the wfs plugin, mostly some package refactoring to isolate version specific code from general one. In my opinion it shouldn't be a problem as its the DataStore nature not to be API, and the only public class should be the datastore factory. Comments wellcome. Regards, Gabriel. ------------------------------------------------------------------------- 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
