There are quite a few cases (and they are increasing all
the time) where the compiled code in Saxon differs substantially from the
original XSLT source. Inevitably this makes it more difficult for operations
like tracing and debugging to link the compiled code back to the source code. It
also means that any user writing a TraceListener has to be prepared for things
to change from one release to the next.
It's true that for many instructions, the InstructionInfo
provided to the TraceListener is actually the StyleElement in the source
stylesheet. But this is simply because that was a convenient way to implement
it, it's not something you should be relying on (it wasn't the case in earlier
releases, and it may no longer be the case in future releases). Equally, the set
of properties that's available for each instruction isn't fixed.
see if there is some way to provide a "select" property on the
would help if you explain what you are trying to achieve with your
Yes - that was
the problem. But how could I get the path in the script and the source now!?
Cause the InstructionInfo is not from type StyleElement I could not get
the path from it.
It should be fixed. However, XSLT local variables are
handled internally as (XQuery-like) "let" expressions, so the
event may not reach the trace listener in the form you expect it. See
the code in XSLTTraceListener:
And if I try to get the path in the select attribute
with instruction.getProperty("select") - I get null. I tryed to get something
But then the path is not the correct
Viele Grüße / best regards
inubit - the integration experts
Fon: +49.30. 72 61 12-132
Fax: +49.30. 72 61 12-100
Freecall: 0800-go inubit