Hi, the 2.0 in the release is there to signify a change. It's the UI, it's the config subsystem.
I was wondering if it could be a good occasion to start being strict about xml request schema compliance? We could have a flag and make strict the default, but allow people to turn that off and fall back on the non strict behavior. I'm asking this because I keep on hearing people confused because the parser just skips over the elements it does not understand and people are left wondering what's wrong. I know that one can append ?strict=true to the url to have schema validation done, the problem is that those users tripping into the lack of error messages don't ;-) Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
