Reviewing gt-xml; it is very much non core. It is simply collecting the first generation gtxml parser design (for some reason I though that the SLDParser and others were here (instead they are still in main).
So that leaves me running in circles... Idea: - move gt-xml to extension/xml (allowing wms and wfs to depend on it) Idea: - move gt-xml to extension/xsd/xsd-old (this would keep it clean; be truthful; and make it obvious what is going on) Idea: - Use the module where it is now - Add in the dependencies mentioned in the previous email - Gradually cut over... Jody On 02/06/2010, at 12:00 PM, Jody Garnett wrote: > After friendly IRC chat with Gabriel... > > Looks like asking gt-xml to take on the task is the best way forward; it > offers a central spot for GML handling that other modules can use. > > My strategy will be to review the wps parser configuration (where it is > configured with with both GML2 and GML3 allowing the XML namespace > definitions to indicate what is going on). I am going to add in the WFS > configuration as well so I can parse OpenLayers feature collections which > extend WFS FeatureCollection. > > So Gabriel is that the right idea? Did I miss anything. > > Jody ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
