However, I'm seeing even more weirdness with this xsl. It seems I can make it work by making changes that have no reason to make a difference. I'd made a number of changes to my copy of your xsl, to try to make it work, and to test that certain things were working property and were not the cause of the problem. I started to clean that up in case it might be useful for the bug submission. But some change I made caused the variable to be passed and make <Display>foo</Display> appear in the output. Trying to backtrack I saw the problem come and go unexpectedly.
I isolated one change that causes the problem to go away. My attached testOK.xsl works properly. testNotOK.xsl exhibits the problem. The only difference is testNotOK.xsl having a "/" template (which was not even in your version and should not be having any effect). I've also gotten other changes that should be unrelated to cause the problem to come and go. It is as if various changes "stir the pot" and activate or deactivate the problem. I realize this makes no sense and makes me sound like a crazy person, but I urge you to try my two attached versions of the stylesheet.
I suspect that issue you had with the key usage using the JDK version was this same "stir the pot" issue and nothing particularly to do with keys, and it probably behaves the same way in both xalan and the JDK version of it.
On 3/10/23 17:05, Bederov, Sergey wrote:
Thank you!The key-related stuff is what caused problems in the JDK version of Xalan. The variable was passed successfully, but then it disappeared when calling the “key” function. I came here to check whether that has been fixed in the official Xalan, but now there is another problem on the preceding step.If it is a bug, then should I report it somewhere? *Sergey Bederov *Senior Developer *Cortona3D** *www.cortona3D.com <http://www.cortona3d.com/>
testNotOK.xsl
Description: application/xslt
testOK.xsl
Description: application/xslt
