Saxon

Bug #1648

Updated by Community Admin over 11 years ago

Bug reported by John Barstow: 

 After some investigation, I've added the following two lines have been added to the 
 Saxon.Api.XsltCompiler constructor: 

             if (config.isCompileWithTracing()) 
                 info.setCodeInjector(new TimingCodeInjector()); 

 After adding these lines and re-compiling, the profiling of XSLT transform I am now able to correctly 
 works. profile XSLT transforms. The -TP flag modifies a default CompilerInfo 
 instance, but the .NET code always creates a new instance, thus losing 
 the code injector. The My solution seemed to be the most surgical fix, but 
 it might be more correct to clone the default instance. I'll let 
 someone with greater knowledge of the Java internals make that call.

Back