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.
I thought about this - we could stick it in the WEB-INF directory. I
thought this might cause upgrade-problems, but I dont think it will.
I'll jira it for a later release.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
Quoting dblasby@anonymised.com:
>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.
I thought about this - we could stick it in the WEB-INF directory. I
thought this might cause upgrade-problems, but I dont think it will.
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.
Chris
I'll jira it for a later release.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/