Saving
Saving XML from Xopus requires that you have a save function. Xopus does not save by itself. You can follow the following steps:
Registering a save function
By registering a save function with Xopus, the application will know what to do when saving.
IO.setSaveXMLFunction(mySaveFunction);
You can find this function in js/save.js of this example.
The save function
The save function itself receives two arguments, uri and document. A simple example of a save function looks like this:
function mySaveFunction(uri, xmlDocument)
{
var result = HTTPTools.postXML("save-xml.aspx?" + uri, xmlDocument, "UTF-8");
return (result.indexOf("error") == -1);
}
The example above uses the HTTPTools object from the Xopus API to send the xmlDocument to the url in postXML.
The third argument is used to convert the XML DOM object back to UTF-8. IE's XML DOM document get a default setting of UTF-16.
Server save code
On the server, depending on the server language you can catch the xmlDocument and write it back to the database. In the code/save-xml.cs file you can find the following code that saves the XML on the server:
StreamReader r = new StreamReader(Request.InputStream);
String xmlStr = r.ReadToEnd();
documentToSave.LoadXml(xmlStr);
documentToSave.Save(filePath);
Returning a string from the server code allows you to process the success of your save code in Xopus (in the client). A lot of examples of this can be found in the How To folder of the other examples in the download.
Permission problems and saving problems
The problem can occur that file permissions aren't set. This often happens when working with actual XML files, but with a database that you save to, similar things might happen. Sessions may expire, which then prevent saving.
To solve these problems, it is is best to check the result that comes back from teh HTTPTools function. You could let the server return a value that indicates an expired session, and consequently show a login dialog to allow the user to continue working, and prevent the loss of data.