<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 19, 2008, at 2:52 PM, Stefan Behnel wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi,<br><br>Paul Everitt wrote:<br><blockquote type="cite">I believe the answer is no. I can't tell if this is part of the spec, <br></blockquote><blockquote type="cite">but docs on other processors imply that you can use a node or node list <br></blockquote><blockquote type="cite">as the value of a parameter passed to a transformation.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In my use case, I'm trying to get information from the current web <br></blockquote><blockquote type="cite">request. I don't want to modify the input document (my normal way to do <br></blockquote><blockquote type="cite">this.) Thus, an XPath extension function or a document resolver will <br></blockquote><blockquote type="cite">have to serve the purpose.<br></blockquote><br>XSLT parameters are passed as strings (char*), so passing subtrees will not<br>work. Passing an XPath expression will work, though, so you can at least refer<br>to all sorts of things that exist in the current context.<br><br>But have you looked at XSLT extension elements? They might do what you want.<br><br><a href="http://codespeak.net/lxml/extensions.html#xslt-extension-elements">http://codespeak.net/lxml/extensions.html#xslt-extension-elements</a></div></blockquote><div><br></div>My challenge is getting at data that was in scope at the time I ran the transformation. The extension element won't have access to that information. I'll be in a threaded environment (WSGI request), so I'll need to arrange to stash the data away in a thread local, then grab it from within the extension element.</div><div><br></div><div>Or??</div><div><br></div><div>--Paul</div><div><br></div><div><br></div></body></html>