Rahkonen Jukka wrote: Hi,
> I wonder how it has been done in a new WFS plugin that can do transactions. > The transaction icon gets highlighted only if something has been modified, so > I think there must be some chance tracking system. And I don't believe really > that anybody makes a WFS-T client that sends the whole layer back if only one > feature is modified. Deegree folks, how is it? well, loading data from a WFS results in a layer that is an instance of WFSLayer. There, all modifications (add/remove/update) are kept track of, and they're then mapped to WFS-T insert/update/delete when the user clicks that button. A layer listener is used so the layer is notified every time the user changes something in a feature or adds/removes one. I think the features are stored in seperate lists depending on what has been done with it. I'm thinking that you'd need the same information for database plugins (you cannot UPDATE a row which needs to be inserted etc.). You can have a look in the WFSPlugin/src/de/latlon/deejump/wfs/jump/ classes, in particular WFSLayer and the WFSLayerListener. 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
