This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Eliot, Easy bit first:
Try test="self::xindr:indirector". You're forgetting that there's an invisible child:: axis in that XPath.Also, why does this fail?: <xsl:for-each select="$direct-result"> <xsl:choose> <xsl:when test="xindr:indirector"> <!-- Never gets here --> When the context node is "xindr:indirector" (as returned by name())? The corresponding template match does work. Is this a subtle side effect of name-space processing?
On the face of it, this would seem to be impossible, since templates aren't really functions, we just use them that way to return RTFs (which some are willing to use extensions to turn back into node sets -- but not the original nodes).What I can't figure out is how to have the resolve-xpointer template return the actual nodes referenced, not a copy of them--is this even possible without writing an extension function that does all the address resolution? That is, I don't see a way for the value of a template to be the direct value of a select action, rather than a copy of the value.
Yet if they contain all the same information, using a node-set extension couldn't you query into them and find the further information you need to continue along your chain?However, my implementation of resolve-xpointer uses xsl:copy-of, which of course isn't going to work because the copy nodes are not the same as the initial target nodes.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |