Re: [Geoserver-users] Updating a layer's bounding box after WFS-T insert

2011-06-14 Thread Ryan Zoerb
#x27;t be applied immediately upon setting > properties of configuration objects. > > -- > David Winslow > OpenGeo - http://opengeo.org/ > > On Mon, Jun 13, 2011 at 5:00 PM, Ryan Zoerb wrote: > I hooked up a transaction listener by adding a bean to the wfs module's >

Re: [Geoserver-users] Updating a layer's bounding box after WFS-T insert

2011-06-13 Thread Ryan Zoerb
he transaction is done, the layer's bounds still show up as 0, 0, 0, 0 in both the GeoServer Web UI and WMS GetCaps. Thanks again for any help, Ryan On Jun 10, 2011, at 12:47 PM, Ryan Zoerb wrote: > I just got around to checking out transaction listeners, and have a couple > questions.

Re: [Geoserver-users] Updating a layer's bounding box after WFS-T insert

2011-06-10 Thread Ryan Zoerb
-+WFS+Transaction+handling+framework and have been looking through the wfs code, but I haven't been able to find any more documentation or examples. Thanks, Ryan On May 23, 2011, at 3:59 PM, Ryan Zoerb wrote: > Thanks for the responses Gabriel and Andrea. I need to get the bounding

Re: [Geoserver-users] Updating a layer's bounding box after WFS-T insert

2011-05-24 Thread Ryan Zoerb
t; On 23 May 2011 16:59, Ryan Zoerb wrote: >> Thanks for the responses Gabriel and Andrea. I need to get the bounding box >> of the actual feature (for zooming to the feature in OpenLayers), so I'll >> give the transaction listener a try. > > Don't you already kn

Re: [Geoserver-users] Updating a layer's bounding box after WFS-T insert

2011-05-23 Thread Ryan Zoerb
Thanks for the responses Gabriel and Andrea. I need to get the bounding box of the actual feature (for zooming to the feature in OpenLayers), so I'll give the transaction listener a try. -Ryan On May 23, 2011, at 11:11 AM, Andrea Aime wrote: > On Mon, May 23, 2011 at 5:50 PM, Gabriel Roldán

[Geoserver-users] Updating a layer's bounding box after WFS-T insert

2011-05-23 Thread Ryan Zoerb
I'm creating a data store from an OpenLayers DrawFeature control, using WFS-T to save the geometry into GeoServer. This works great, except the data store's bounding box doesn't get set in GeoServer. However, if you create a data store from a shapefile, the bounding box gets automatically set. I

Re: [Geoserver-users] [ExternalEmail] Re: App schema feature chaining issue

2010-11-05 Thread Ryan Zoerb
Sorry for the delay. Yes, publishing GWSI_LEVELS as a WFS simple feature works. Thanks, Ryan On Nov 4, 2010, at 8:46 PM, Ben Caradoc-Davies wrote: > Ryan, > > please publish GWSI_LEVELS as a WFS simple feature. What SQL do you see in > the logs when you query it? > > If you see the invalid c

Re: [Geoserver-users] App schema feature chaining issue

2010-11-03 Thread Ryan Zoerb
gt; support, or an unintended interaction with your database configuration. I > cannot find any hardcoded identifier "TIMES" in the code base. > > (1) Is GWSI_LEVELS a table, view, or materialized view? > > (2) What is the output of "DESCRIBE GWSI_LEVELS"? >

[Geoserver-users] App schema feature chaining issue

2010-11-02 Thread Ryan Zoerb
Hi everyone. I'm trying to get application schema with feature chaining working, but I'm running into an issue. I've attached the two mapping files I'm using. WaterWell is the top level element, which can have several nested logElement's. I've been able to successfully get GeoServer to retur