Saxon

Hello,

unfortunately I couldn't find any hint on my problem in the change log of Saxon 9.6:

The current version of my application uses Saxon9.5.1.3J for transformation jobs and is running on JDK1.7.0_72. To prepare the step towards JDK1.8 I'll have to switch to Saxon9.6.0.5J (-> Java8 manifest format). During my tests I recognized that the execution of transformations with xsl-templates produced "Recoverable Errors XTRE0540" and the results were not longer correct. The Problem remains running the tests on JDK1.8.0_25.

The execution order of concurrent templates seems to have changed from "most specific" to "last one in template". This suggests that there may be a change in the determination of the default template priority based on the matching xpath expression.

I know one solution could be to assign explicit priority values to each rule but that would be a really time consuming Job considering the bunch of templates my application is handling...

Can anyone tell me whether the behaviour described above is a bug or an intended change? Can I do anything (implementation, parameterization, configuration) to cope with this problem apart from reviewing and re-writing our complete (partly generated) rule portfolio?

Below you see one simple template which works really well with Saxon9.5.1.3J while with Saxon9.6.0.5J it produces the shown warning and generates results that show the wrong "last one in template" execution:

Recoverable error 
  XTRE0540: Ambiguous rule match for /Document
Matches both "*[namespace-uri()=$nsUriOld]" on line 23 of 
and "/*[namespace-uri()=$nsUriOld]" on line 8 of

If I'd need to provide any further Information please ask.

If anyone can lead me out of this unlucky situation, thanks in advance!

Regards eike2k