Justin Deoliveira ha scritto: > Hi all, > > Recently it was required that GeoServer have the ability to disable wfs > 1.1. So what I did was moved wfs 1.1 to a new module so that to disable > wfs 1.1 all one must do is delete the jar for that (new) module. There > should be no difference for the normal user.
Wow, the patch looks... big! :) At a quick look the size is due to some changes to the EMF models that now have a "provided version", and then I see changes in the response class hierarchies... could you very quickly summarize what you did so that we can orientate in the new code structure? Like in a bulleted list of short statements, something that gives a feel of the change. No need to be fancy :) > However this solution is far from ideal and I have not committed it to > trunk. On trunk I think we should use the new configuration to model the > versions of a service which are enabled. And indeed the ServiceInfo > interface has a getVersions() method for this purpose. Hooking our > services up to will take some work but i believe its the right way to do > it. Others may disagree. Yeah, I agree this seems like a better approach. I guess this could be done in the dispacher no? In the dispatcher you already determine the service and version, so if you have the list of enabled services _and_ enabled versions you "just" have to perform a comparison, and if the version is missing, just assume the highest enabled version? Cheers Andrea ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
