-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SXWN9000 for text node rule #11
Comments
Replacing https://github.com/dmj/schxslt/blob/086a08182532eac7376dceaf191c3046bf498542/src/xslt/compile.xsl#L258 <call-template name="schxslt:handle-attr-and-children"/> and relocating |
This curently works, indeed. But I don't think that this is a viable solution: Saxon issues the warning during static analysis. It might be just a matter of time until Saxon catches up. Maybe suppressing Saxon warnings alltogether is an option? If not, we could utilize @use-when and create different paths depedning on the xsl:vendor system property. But this should be the last resort. |
Addendum: With queryBinding xslt3 the solution would be xsl:mode on-no-match=shallow-skip. I currently need the apply-templates call b/c the built-in template rule for elements ignores the attribute axis. |
No, this is not true. Still need to apply to @* when an element has matched. |
Right, the viability depends entirely on Saxon's evolution. |
This problem is solved: SchXslt now uses "ex-post rule match selection" by default. I.e.: The validation stylesheet chains rule templates with xsl:next-match. |
…lt-schxslt-1.4.5 Bump schxslt from 1.4.2 to 1.4.5
When I have a rule on text
then the compiled stylesheet generates a warning
Could this be avoided?
Using Saxon 9.9.0.2.
The text was updated successfully, but these errors were encountered: