Saxon Output current Template Name/Runtime Context

iceandrews · April 27th, 2015, 02:03 PM

Is there a method to output the current template name/match in the output nodeset? I've looked through the Saxon Extensions/Functions and other library functions and I can't find this capability.

So if I have a <xsl:template match="X[Y]"> or <xsl:template name="FUBAR"> I'd want to put the "X[Y]" or "FUBAR" into the output XML. Is this possible?

I know if you turn on Timing Profiling (-TP) you get that information in the timing of each template match/name. But this is coming form the java code running on the processor, not the XSLT itself.

samjudson · April 29th, 2015, 04:29 AM

The only way you would get the output you are asking for into the output nodeset is if you do it manually. I don't think there is a way of getting the current template selector though, so you will just have to do something like this:

Code:

<xsl:template match="X[Y]">
   <template match="X[Y]">
   ...

iceandrews · April 29th, 2015, 08:39 AM

Yep, that's the hard coding that we fell back on for our needs. I was hoping there was a dynamic way with extension instructions/functions so we didn't have to update those if we made changes.. The saxon processor know that information, so I thought there might be a way, but I couldn't find in the documentation.

Thanks anyway.

mhkay · April 29th, 2015, 09:08 AM

The interfaces are there in Saxon if you want to attempt it, but you'll have to grovel pretty deep. When you use -T (or -TP), Saxon does two things: firstly, at compile time it applies a CodeInjector which inserts extra code into the expression tree. Then at run-time, it supplies a TraceListener, which gets called at selected points by this injected code. You could exploit this to achieve the desired effect by writing a TraceListener which leaves the data you want "in a well known place", and then have an extension function which retrieves it from there.

But a simpler way, I think, would be to run an XSLT transformation on the stylesheet that generates xsl:message instructions at the start of each template rule.