input.xml seems to be totally irrelevant to the example XUpdate document (xupdate.xml).
Yes, that's right. In this case the input document does not matter, as we the XUpdate program just completely replaces the input document with its own computed document. The input document could as well be something like <dummy/>. We have here more complex input document so you can test in the sandbox a XUpdate program what would actually use the input document in a meaningful way.
I don't understand the OXF XUpdate driver example 100% (http://www.orbeon.com/oxf/doc/integration-xupdate)
Just let me know if there is anything else that is not clear in the program.
The createTemplates() function takes an XML doc parameter (xupdate.xml) which is the XUpdate document defining nodes and values to update a target document. The target document (input.xml) is modified with the update (or the output of the driver is an updated instance of input.xml). This target document must also match the exact structure expected and defined within xupdate.xml.
That sounds about right. By the way, the XUpdate engine just implements the JAXP API (to be precise: part of the JAXP API, as described in http://www.orbeon.com/oxf/doc/integration-xupdate). JAXP is often used to run an XSLT transformer, with a stylesheet, input and output document. Here we just have an XUpdate engine, with an XUpdate program, input and output document. It is conceptually very similar to XSLT, except the program is not written in XSLT but in XUpdate.
Alex
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
