Hi all,
I have a question about relative URLs in SLDs, (really a question about the "right thing" for the CSS converter to do with them).
When I try to use a relative image URL in a CSS stylesheet, everything goes well until the encoder tries to write it out, as which point I get an exception claiming someone CODED THE XLINK NAMESPACE WRONG!! I guess a regular string is okay up to this point, but at output time something tries to parse the image reference as a URL and blows up. I haven't tried feeding the generated Style object directly to the renderer though.
This raises a bit of a red flag for me because we are using relative URLs in the default datadir and recommending them to users in places like the SLD cookbook (which is what I was looking at when I ran into this). Should the GeoTools SLD encoder be more lax in this case, or should we be warning users about using relative URLs in their styles?
fwiw, I would like to see relative URLs stay since without them I'll have to convert relative paths in CSS styles to resolved absolute URLs in SLD, and then have all of them break when you move your GeoServer data directory.
--
David Winslow
OpenGeo - http://opengeo.org/