On 26/02/2025 15:59, Mukul Gandhi wrote:
Hi Alan,
I've just seen this mail from you. Apologies for a delayed response.
My mail box has had few issues due to the volume of mails that I get
from mailing lists.
On Sun, Feb 2, 2025 at 9:38 PM Alan Bateman<alan.bate...@oracle.com> wrote:
The stats for that branch suggest 5,845 changed files with 234,372 additions
and 84,058 deletions. I can't easily tell how much of this would need to come
into the jdk repo but this looks like a major update. If only 10% of this is
applicable to the JDK then it still needs seems like a major update that would
require a huge investment to audit and integrate this code. How much XML is in
new applications developed in 2025? Only asking because it's an area that is
surely much lower priority compared to all the other major investments right
now. Maybe there are useful security or performance changes that would be
useful to cherry pick instead? Finally, does this Xalan update work with the
SPIs so that someone really looking for XSL 3 can just deploy it on the class
path and module path?
Ofcourse, anyone could use Xalan-J's XSL 3 implementation with JDK by
placing Xalan jars on class path & module path.
Can you clarify if this is using javax.xml APIs, with Xalan-J deployed
as an implementation, or this some Xalan-J specific API?
Since Xalan-J's XSLT 1.0 & XPath 1.0 implementations are already
available within JDK, I thought its natural if JDK could pick
Xalan-J's XSL 3 implementation and include that within JDK.
Are you sure that developers are clamoring to develop new code that uses
XML and XSL 3? It would require a big investment by JDK maintainers to
audit and review this huge volume of code. The priorities for the XML
APIs/implementation right now are on making XML processing be secure by
default and bringing sanity to the configuration of applications that
still use XML. This is the reason for the incremental improvements in
recent releases.
If you are interested in contributing to the XML implementations in the
java.xml module then this would be welcomed. It's always better to start
small with bug fixes, test improvements and other changes to get used to
working in this project and build up confidence that you are someone
that is interested in maintaining this area in the long term.
-Alan
