On Tuesday, 14. January 2003 19:58, S Woodside wrote: > Also, what server-side method do you use for this? Do you use XSP? I'm > not sure how to catch the GET/POST parameters in XSLT alone (if that's > even possible?) although I'd prefer to keep it in straight XSLT if > that's possible.
I use XSP for the processing, as described in the other mail. In XSLT, you can (have to) declare parameters with <xsl:param>, this way you can access GET/POST query data. But as you can't declare them dynamically, there is no way to 'just get all of them'. > It would be super-sweet if XSLT had a way to serialize the "current > node" context in the tree it's parsing into a string, then I could pass Serializing into a string? like this? <xsl:template match="*"><<xsl:value-of select="name()"/><xsl:apply-templates select="@*"/>><xsl:apply-templates/></<xsl:value-of select="name()"/>></xsl:template> (imagine similar templates for text() and @*, including quoting of &, < and ") That is, make a string from the node set? > that back, "deserialize" it in the XSLT and just select="..." to jump > to that node, and then copy-of the subtree from there on to my form.xsl > (but I didn't find anything like that in the XSLT spec) If I understand you right, "Deserialize" == parse? That's the difficult part, you can't parse an xml string passed in as parameter, only stuff included via document() gets parsed. As for storage/output, there is something in EXSLT which lets you create files. Might have to be implemented in libxslt, but we are programmers, are we? :-) -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
