Hi, the build failure you've seen is due to the URL manglers GSIP and me not checking the app schema module.
The issue there is that the new ResponseUtils.buildURL method does actually url-encode all kvp parameters. And this is a good thing, right? Well, yeah, but it turns out we used to put in the various URL we generated characters like the comma or the column that are actually reserved chars which are not supposed to be found in a URL, see here: http://www.blooberry.com/indexdot/html/topics/urlencoding.htm http://www.permadi.com/tutorial/urlEncoding/ http://en.wikipedia.org/wiki/Percent-encoding and there is an online url encoder, decoder: http://www.albionresearch.com/misc/urlencode.php So, if I'm not reading the above documents wrong, the current behavior is correct and some tests needed to be fixed and url-decode the urls contained in our xml documents before trying to split them on "," or checking equality with strings containing a column. I'm still a bit surprised about this finding but... here it goes. If you know more about this topic and care to share it I'll be all ears 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
