I have one GeoServer (A) with another configured as a deligated WFS (B).
If I publish a layer in B then go to A and try to publish that (deligated)
layer, then I can't because (A) won't have done another GetCapabilities on
(B) to see the new layer.
If I restart (A) then all is fine as it does a GetCapabilities on (B) at
startup - that's rubbish though.
If I remove then re-add (B) through the GUI as a deligated WFS store then
all is well as it does a GetCapabilities when I go to add the new layer -
this is 'ok ish' but not what I want
I'm trying to force (A) into a GetCapabilities of (B) through the RESTful
interface but it seems impossible. If I 'reload', then no GetCapabilities
on (B) is performed and I get the same list of layers I had from the
original GetCaps. If I add/remove the datastore through REST then the GUI
confirms the operations are working but the GetCaps is never re-performed
and the same (original) list is ALWAYS presented to me. This is wrong
surely. The docs say the cache is cleared but a GetCaps is NEVER performed
more than once in the same run session for a particular (WFS) url. If you
change the url of the (B) datastore to a new one (C) through REST then
GetCaps is done on (C), but put it back to (B) and it thinks it's already
done it.
Basically it looks to me that there is a list of urls that have been
GetCap'ed and that list survives a 'reload'.
Please can someone either tell me I'm wrong or tell me how to get a store to
reissue a GetCaps through the RESTful interface
Thanks
--
View this message in context: http://old.nabble.com/REST-reload-doesn't-clear-all-caches-tp30057702p30057702.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
Hmmm… i would expect that when a reload occurs as the resource cache is cleared the wfs datastore should be recreated and do another getcapabilities request. But it seems that is not the case. I am not that familiar with the wfs datastore… how does it cache the capabilities document? I guess with some sort of static cache. I would say this is more a bug with the wfs datastore not cleaning itself up on dispose.
On Tue, Oct 26, 2010 at 7:49 AM, monkeyboy9364 <jason.mardell@anonymised.com> wrote:
I have one GeoServer (A) with another configured as a deligated WFS (B).
If I publish a layer in B then go to A and try to publish that (deligated)
layer, then I can’t because (A) won’t have done another GetCapabilities on
(B) to see the new layer.
If I restart (A) then all is fine as it does a GetCapabilities on (B) at
startup - that’s rubbish though.
If I remove then re-add (B) through the GUI as a deligated WFS store then
all is well as it does a GetCapabilities when I go to add the new layer -
this is ‘ok ish’ but not what I want
I’m trying to force (A) into a GetCapabilities of (B) through the RESTful
interface but it seems impossible. If I ‘reload’, then no GetCapabilities
on (B) is performed and I get the same list of layers I had from the
original GetCaps. If I add/remove the datastore through REST then the GUI
confirms the operations are working but the GetCaps is never re-performed
and the same (original) list is ALWAYS presented to me. This is wrong
surely. The docs say the cache is cleared but a GetCaps is NEVER performed
more than once in the same run session for a particular (WFS) url. If you
change the url of the (B) datastore to a new one (C) through REST then
GetCaps is done on (C), but put it back to (B) and it thinks it’s already
done it.
Basically it looks to me that there is a list of urls that have been
GetCap’ed and that list survives a ‘reload’.
Please can someone either tell me I’m wrong or tell me how to get a store to
reissue a GetCaps through the RESTful interface
Thanks
View this message in context: http://old.nabble.com/REST-reload-doesn%27t-clear-all-caches-tp30057702p30057702.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.