On 10/04/2026 10:24, Mukul Gandhi wrote:
Hello OpenJDK team, I've prepared Xalan Java XSLT 3.0 JEP draft document (in required Markdown markup language), attached with this mail as a file.Please review the attached document, for its appropriateness, to help formally submit this mentioned JEP by an existing OpenJDK committer. Perhaps Alan Bateman may become sponsor of this JEP.
Do you have a sense as to whether new applications are being developed today that use XSLT? What is so compelling about XSLT 3.0 and Xpath 3.1 that would would be exciting for developers?
It would be a huge undertaking for the JDK to take on several hundred thousand lines of Xalan code, review all the code and work through all the security and compatibility issues. This is before being prepared to maintain it for the next 10+ years. The bar for bringing in something like this is really high and it's not just not clear if there are compelling reasons to spend time on it.
In the other thread you confirmed that it works as a library on the class path or module path today. Aside from the inconvenience of adding it as a dependency, what is the downside to what is possible today? Can developers use the javax.xml APIs with the new Xalan deployed as a service provider.
-Alan.
