Rob Atkinson ha scritto: >> Can you make me an example of "getting the info from the optimal place >> in the optimal way"? Afaik with the current configuration API we have >> just one place to grab each information we need to build up a UI, >> and this sounds like a very good thing (TM) imho. >> > > OK, for example, we specify namespaces in several locations (schema, > info, datastore config, catalog file, SLD), but they should all be > inherited from the target schema (yes I know I'm talking about > community schema support, but there is very little requirement for WFS > without it - do you see many deployed?)
In production? Tens for sure, probably more. Community schema is a nice to have, but lack of it did not stop people from deploying WFS server all around the world. Why do you have to put community schema as a requirement for everything that has to be done in GeoServer is frankly beyond my comprehension. I won't discuss this any further, since this is about feature type configuration, not about the UI framework. Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
