[Karl Stubsjoen]
I'm considering maintaining an XML object (string) in a form
post... What are the potential pitfals? I'm writing a little
maintenance screen which collects information and stores it
in an XML document. There are many form posts (many trips
back to the server). Is this a good idea? If not, is there
a better way to maintain this XML document?
I have done this. I used xslt to create the form from the previous
version of the xml document, and included enough hidden fields to
recreate the xml document for each new post (I did not have to have a
hidden field for each element - the stylesheet created most of the
document, so I only had to include certain customized items). Actually,
this system handled workflow, adding and changing specific data as the
work moved along from station to station. It worked very well - at
least, as a simple prototype demonstrating the principle.
I know some people have used path expressions for naming form elements,
and used those expressions to control where the data would get inserted
into the result.
Cheers,
Tom P
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list