Hi Alan, Thanks for your reply. Apologies that I've responded with a delay.
On Mon, Apr 13, 2026 at 10:12 PM Alan Bateman <[email protected]> wrote: > The draft JEP (attached to your first mail) makes no mention of changes to > the javax.xml.transform API. The code example seems to be using a mix of > javax.xml and org.apache.xalan APIs. > > I think it would be useful to get a summary of what works and doesn't work > when Xalan-J XSLT 3.0 is deployed on the class path or module path as a > service provider. Assume the application code restricts itself to the > javax.xml APIs, can it get a Transformer from a source that is XSLT 2.0 or > 3.0? I'm trying to set a sense as to whether there are API changes or not. I think that, I'm not the right person to draft JEP for JDK. You may please look at Xalan-J's XSLT 3.0 alpha1 release notes (again, perhaps) available here, https://xalan.apache.org/xalan-j/xsl3/release/alpha1/RELEASE-NOTES.txt After Xalan-J's XSLT 3.0 alpha1 release, there are few new implementation changes within Xalan's XSLT 3.0 development branch. The latest status for this is available here, https://xalan.apache.org/xalan-j/xsl3/xalanj_xslt3.0_implementation_status.pdf JDK I think, primarily provides XSLTC to users, and not Xalan-J's interpretive processor. Xalan-J XSLT 3.0 development code provides only an XSLT interpretive processor. Many thanks. -- Regards, Mukul Gandhi
