Saxon configuration option TimingTraceListener
Posted: Mon Mar 04, 2019 9:41 pm
Hi guys,
to take advantage of the simpler timing feature built into Saxon I added a Saxon configuration file to my transformation configuration (Advanced Options), with the following content:
That works great!
But if I have "Additional XSLT Stylesheets" selected, the profile.html contains only information from the very last XSLT run, apparently because the filename is the same for all invocations, and therefore the last one wins.
Could you please consider to:
A) Add this option directly into the Saxon options
B) Allowing to trace a full transformer pipe, e.g. by allowing some variables in the output filename, like ${cfn}
As always, I would be glad to hear some method how to achieve my request with the product out-of-the-box (version 21)
Best regards,
- Michael
to take advantage of the simpler timing feature built into Saxon I added a Saxon configuration file to my transformation configuration (Advanced Options), with the following content:
Code: Select all
<configuration edition="PE" xmlns="http://saxon.sf.net/ns/configuration">
<global traceListener="net.sf.saxon.trace.TimingTraceListener"
traceListenerOutputFile="/Users/michael/Downloads/profile.html"/>
</configuration>
But if I have "Additional XSLT Stylesheets" selected, the profile.html contains only information from the very last XSLT run, apparently because the filename is the same for all invocations, and therefore the last one wins.
Could you please consider to:
A) Add this option directly into the Saxon options
B) Allowing to trace a full transformer pipe, e.g. by allowing some variables in the output filename, like ${cfn}
As always, I would be glad to hear some method how to achieve my request with the product out-of-the-box (version 21)
Best regards,
- Michael