location of capabilities/ directory

Description

After the conf/ configuration re-org so they could be pointed to directly by the geoserver_data_dir, I found that all the configurations required the same capabilities/ directory.

I just copied the capabilities/ directory into each configuration - a better idea would be to move this to the WEB-INF/ directory so there's only one to maintain.

Consider doing this - make sure that there's no upgrade problems and capabilities really isnt changing.

cholmes:
>Hmmm... I wonder if we could/should put the capabilities directory in a
>more static place? Is it the only thing in the data dir that will
>always be the same across configs? Because I think we will have to add
>more, like when we add new ogc services.

Environment

None

Activity

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

CodeHaus Comment From: dblasby - Time: Mon, 9 May 2005 08:30:04 -0500
---------------------
<p>Actually that won't work. Putting things in WEB-INF hides them - the

reason we have the capabilities is so that our xml validates - we point

responses at their location in geoserver, so we're not relying on some

other web resource. Any validating xml reader will follow the

pointers, and fail if we don't provide them. Thinking on this, having

capabilities in the data dir simply won't work, since they won't be

available in the web app (or did you manage to come up with a work

around for this?). If the data dir is not always available in the web

app we probably should have another directory that is, where we can

stick such resources.</p>

<p>Chris</p>

codehaus
April 10, 2015, 4:14 PM

CodeHaus Comment From: aaime - Time: Thu, 29 Mar 2007 02:06:11 -0500
---------------------
<p>These issue has been in resolved state for at least one month (quite a bit, a lot more than one month). Batch transitioning them to closed state</p>

Fixed

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

Affects versions

Components

Priority

Medium
Configure