In the Advanced section of our Tutorials there are two, numbered 330 and 362, that address our support for interacting with Web services.
We currently do not support saving changes to Web services. We plan to implement such support in the future but at this point in time I can't give you a definite time frame for implementing that support.
The text in the Developer's Guide was added at the time that our Web Services support was first added. There are many possible sceanarios for the usage of Web services in an application built using DevForce as well as Web service applications built through other means. The many possible scenarios have not been thoroughly tested. We have not seen extensive problems reported against our Web service support but we do not yet consider this functionality to be mature.
In response to one of our customers who was looking for a way to work around our limitation of not supporting writing to Web Services "out of the box", however inelegant, one of our support engineers proposed the following solution:
1) Publish your rdb based entities as a web service
2) Caller retrieves data using currently available WS publishing functionality
3) Caller modifies data in ADO.NET dataset
4) Caller sends modified dataset back to a web service method (doesn’t yet exist)
5) This ADO.NET dataset is loaded into a persistence manager similar to the way we load from the file system
6) Server validates/verifies/whatever and returns some sort of XML package back to the caller indicating success/failure/etc. state of the process