maven test fails for gmldatasource preventing full build

CodeHaus Comment From: cholmes - Time: Mon, 5 Apr 2004 10:19:27 -0500
---------------------
<p>I just decided to do away with the schemaBaseUrl for 1.2.0. Hopefully no one will complain, but I don't think anyone understood what it was anways. It started as a hack since I didn't have the xsd files referenced locally. It was never possible to determine wher eyou wanted those files to be, they have to be in data/capabilities, and it'd be a bitch to implement that otherwise (rebuilding the war I think, though there's probably a way to do it programmatically, but I don't know it). But I'm just crossing my fingers no one wants this at all. </p>

CodeHaus Comment From: brihaye - Time: Sun, 14 Mar 2004 07:03:16 -0600
---------------------
<p>&gt;The schemaBaseUrl is actually completely wrong. It shouldn't be a local file at all. It's a pretty obscure option, basically it should be a url where the schemas that geoserver refers to are located. </p>

<p>That is clear.</p>

<p>&gt;So basically that field needs to be left blank</p>

<p>That lakes sense.</p>

<p>&gt;or to say something like 'local'</p>

<p>Mmmh... as we are in a servlet environment, I think it would be better to provide a contextualized URL, i.e. <a href="http://server:port/geoserver/whatever/wherever/" class="external-link" rel="nofollow">http://server:port/geoserver/whatever/wherever/</a></p>

<p>p.b.</p>

CodeHaus Comment From: cholmes - Time: Sun, 14 Mar 2004 04:35:14 -0600
---------------------
<p>The schemaBaseUrl is actually completely wrong. It shouldn't be a local file at all. It's a pretty obscure option, basically it should be a url where the schemas that geoserver refers to are located. GeoServer now stores its own schemas, and the default should be the locally referenced ones (in geoserver/data/capabilities I believe). The user interface actually does absolutely nothing to set these. So basically that field needs to be left blank, or to say something like 'local'. The sort of option that one would use it for is to say reference schemas hosted elsewhere, like if a user did not want geoserver being hit with all the validation requests, they could install it elsewhere. An example of a valid schemaBaseUrl is <a href="http://schemas.opengis.net/" class="external-link" rel="nofollow">http://schemas.opengis.net/</a> The schemas here are ordered properly. But yes, this field does need to be fixed, but not absolutized, since the initial guess of the default value is just wrong.</p>