Hi Eric, Thanks for that. BTW what is the reason for creating the 'phantom' record in the store?
At the point at which it's created in FeatureReader.readRecords() it already has an OpenLayers ID, could that not be used as it is when the feature is not in an INSERT state? Cheers Adam On 21/05/2010, at 11:07 PM, Eric Lemoine wrote: > On Fri, May 21, 2010 at 10:26 AM, Adam Ratcliffe <[email protected]> wrote: >> Hi Eric, >> >> The feature is a new feature that's created with the >> OpenLayers.Control.DrawFeature control. The feature belongs to a WFS layer >> and is saved via its Save strategy. It seems the FeatureStore is unaware of >> the change in the feature's state when the layer is saved. > > Right. > > At this point I don't know where this should be fixed. In the mean > time you should be able to fix it in your application, by registering > to the save strategy's "success" events and taking appropriate action > in the listener. > >> >> Am I seeing this issue because the FeatureStore expects the layer to be >> saved via the store's save() method only? > > No. Currently GeoExt doesn't calling save on a feature store. > > > Hope this helps, > > -- > Eric Lemoine > > Camptocamp France SAS > Savoie Technolac, BP 352 > 73377 Le Bourget du Lac, Cedex > > Tel : 00 33 4 79 44 44 96 > Mail : [email protected] > http://www.camptocamp.com _______________________________________________ Users mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/users
