mirror of
https://github.com/alexandrev/xslt-lab.git
synced 2026-09-13 08:43:16 +00:00
claude-code
053a7d95e5
Three things the error review turned up. Secure processing caps an XPath expression at 100 operators, so the JDK was refusing perfectly valid stylesheets with JAXP0801002 — a limit this service imposes, not a mistake by the author. The XSLT 1.0 daemon now raises the op, group and total limits instead of switching secure processing off, which also guards external entity access; a runaway expression is still bounded by the 10s transform timeout, and any -D on the command line still wins. That error is now classified as "backend" rather than "stylesheet": it belongs with the bug candidates, not with user error, or the dashboard hides it. The remaining unclassified errors were mostly classifiable all along, and the patterns come straight from the production logs: multiply-defined and undefined variables, format-number picture strings and missing Java extension methods are the author's stylesheet; a stray <?xml ...?> declaration is the input document. Finally, calls to Java extension methods now say so: the playground runs stock Saxon HE, so a class from the author's own project or their ESB runtime will never resolve, and the raw "Cannot find external method" gives no clue why. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KZntQUfw463NW4ftgSjWw5