Move capabilities/ schema information to top level directory

Description

A big problem with the first iteration of the data_dir was that the capabilities directory (which is mis-named), with the schemas, was in the data_dir, so that if the dir was not in the webapp, they wouldn't get referenced properly. This should move to its own directory, alongside data, and the guys who need it should call it directly. This should be easy to implement, since they already grab the location of that directory from a central place - util/Requests.java.

Environment

None

Activity

Show:
codehaus
April 10, 2015, 4:23 PM

CodeHaus Comment From: cholmes - Time: Thu, 24 Nov 2005 09:11:59 -0600
---------------------
<p>This should all be moved, deleted all the individual cite conf ones, since each had its own. Got rid of the top level capabilities/ directory, since it seemed to never be used. Replaced it with a directory called schemas/ which is a much more sensible name, since that's what it stores. Also killed the random 0.15 wfs version wsdl and weird capabilities stuff. Changed Requests.getSchemaBaseUrl() to reflect the new schemas directory (changed the build file so it gets copied in at the war level, which is where everyone uses it), and tested with xerces validation. r3952 to r3955</p>

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

Affects versions

Components

Priority

High
Configure