- From: Flinton Adam <Adam.Flinton@cfh.nhs.uk>
- Date: Thu, 2 Feb 2006 21:24:13 -0000
- To: <www-forms@w3.org>
Dear All, We have a system which uses XSLT to Transform some XML into XHTML. When the transform runs, it takes a note of the Xpath to that element in the XML & puts it into the XHTML as a link to a popup which is used to edit that small chunk of a much larger document. i.e.: 1) The Servlet loads the XML file & holds onto it as a DOM in a hashtable key'ed using it's url/filepath-name. 2) The XML is then rendered into a viewable (XHTML form) via an XSLT sheet. 3) The XLST puts in the Xpath of the pretransformed XML element into the XHTML as a link. 4) Clicking on that link makes the servlet use Xpath to pull the contents of the XML element out as string & send it to a popup. 5) You do your editing in the pop-up 6) Clicking save posts the (changed) contents back to the servlet as string & it is placed back into the DOM using the same Xpath which originally extracted it. Wht I am wondering wrt Xpath is that we need to post back various hidden form values such as the xpath, the url of the file (which is the key to get the relevant DOM) & a value to say it's a op-up posting back so plaease put it into that DOM using this XPATH. Given I would like to use Xforms to do this as I can save on transforming XML > XHTML > XML in the popup, where would I be best off putting these values? i.e. at present the servlet would simply receive the XML Instance w/o the relevant url & xpath to insert it back in. I can obviously create a 2nd model to store the information as it comes in so I can post it back, however it's the actual posting back I am asking about i.e. is my only option to put these values within the url I am posting e.g. some kind of MyServletURL/?xpath=/mynode/ etc? TIA Adam This e-mail is confidential and privileged. If you are not the intended recipient please accept our apologies; please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Thank you for your co-operation.
Received on Thursday, 2 February 2006 21:24:20 UTC