hmmmm, I like your second idea (too many parameters to make it a function --
would get messy)...so you're saying something like the following should work?
<xsl:variable name="myvar">
<http:queryString>
<param name="1" value="1"/>
<param name="2" value="2"/>
</http:queryString>
</xsl:variable>
I wasn't aware you could put body text in xsl:variable, but if that works
that's a great solution.
So to return data to the parent, do I just do
xslProcessorContext.outputToResultTree(...)
from within my extension element?
Number 1 in Truck Insurance
______________________________________________________________________
CAUTION - This message is intended for the addressee named above.
It may contain privileged or confidential information. If you are
not the intended recipient of this message you must not use,
copy, distribute or disclose it to anyone other than the addressee.
If you have received this email in error please return the message to the
sender by replying to it and then delete the message from your computer.
Internet e-mails are not necessarily secure.
National Transport Insurance does not accept responsibility for changes made to
this message after it was sent.
______________________________________________________________________
