I agree that storing well-formed XML data is the
ideal here... the solution you propose is one which
(a) works on a single field, and (b) stores that field as a CLOB in a RDB
Right?
Wrong :)
a) it works on any number of fields you want, just call it multiple times.
b) parses that field and returns a DOM. If you had an XML database that supported documents as native types, you could maybe store that directly.
I am trying to solve the problem of having
the data from a number of CForm fields stored back into
an XML file using the existing CForms framework. So, a "simple" (to me) solution is one which identifies where and how I insert the code-call you have written into the exisiting framework.
You could insert it right after the call to form.showForm(). You could, for instance, use the forms binding framework for all fields of the supported datatypes, and manually retrieve and parse just the HTML fields.
This probably means writng a couple of flowscript lines per each usage of the form, which is not a big deal, but if you wanted to have transparent support for this kind of use-case, adding an XML datatype and convertor to CForms could be a valuable addition to the framework. It just takes someone with an itch to scratch ;).
Ugo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
