Paolo Rizzi wrote: Hi,
> > We play with WFS-T at work, where the mechanism of what really happens > > finally is hidden behind datastore drivers of WFS server like Geoserver or > > others. Anyhow, the problem is still the same than with direct connections > > to database. For example this document is handling rather similar situation > > and may be refreshing reading. > > > > http://geoserver.org/display/GEOS/Versioning+WFS+-+Sample+calls > If I remember well WFS-T has an advantage in this respect, because when > you insert new features, you send them without the PKs and the server > _answers_ back with the very same content you sent, but with the PK > values it generated. > So in the very same transaction you send your new Feature and obtain > their generated PKs. With JDBC alone this can't be done, I believe... > Anyway a WFS-T inspiration is surely useful!!! Yes, that's true, an wfs:Insert request will respond with the feature ids that have been generated (provided you insert with idgen="GenerateNew"). Also, WFS knows GetFeatureWithLock and LockFeature requests, so you can edit and update features safely (to get back to the previous discussion). The problem here is, that at some point you'll have to know how the database is setup, either when working with the DB directly, or when setting up the WFS ;-) Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-12 fax ++49 +228 1849629 http://www.lat-lon.de http://www.deegree.org
signature.asc
Description: Digital signature
------------------------------------------------------------------------------
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
