At 05:36 PM 3/31/03 +0100, you wrote:
> yikes! - looks like the simplest way is to have:
> <xsl:template match="name">
> <xsl:for-each select="ancestor-of-self::*">
> <xsl:value-of select="name()" /><xsl:text>/</xsl:text>
> <xsl:value-of select="." />
That won't work if you want to generate a path that's independent of the
If you want the path expression to be
context-independent then you need to generate steps of the form
*[local-name()='x' and namespace-uri()='y']
you lost me there. i can assume that there will be only one namespace in
use or none for my case,.
Also, the code above generates a path such as a/b/c/d which will select
many elements, whereas you probably want one that selects a single
element such as a/b/c/d.
yes, i do have arrays and will want to solve that problem. but i could use
number on the names of the elements perhaps?
But in this case the "tumbler"
path of the form */*/* is simpler, and avoids namespace
i need to know the names, because i need to know what i am doing when i
process the elements. the xpath names will be he values of name attributes
in an html form.
As you see, there are multiple solutions to this requirement - which is
because there are actually a number of different requirements. This is
why there is no standard function.....
i can see this.
is there any way to get at it using type(), like test="type()='ENTITY") or
something like that?
ray tayek http://tayek.com/ actively seeking mentoring or telecommuting work
vice chair orange county java users group http://www.ocjug.org/
hate spam? http://samspade.org/ssw/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list