I'm using Saxon 8.7.3 from ANT to do XSLTs with the 'key' function. The first parameter value of the key function in this case is an XSL parameter. This works in most of the situations I've used it, but I've got at least one XSLT using this approach where this exception happens:
java.lang.IllegalArgumentException: Unknown name code -1
In 8.7.1 this same XSL gets a NullPointerException due to bug 1491444, which is fixed in 8.7.3. Now that the fix is applied to avoid the NPE, is there a way to find out the name string for the unknown name code so I can determine what is wrong?
Sounds as if the fix was incomplete. Specifying the key name at run-time is a fairly unusual path so it doesn't get all that well tested. It would help if you could post an example that demonstrates the problem. (You can upload attachments to the "support requests" tracker - cross reference it from here).
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.