[
https://issues.apache.org/jira/browse/XERCESJ-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365419#comment-16365419
]
Mukul Gandhi commented on XERCESJ-1689:
---------------------------------------
I've done some quick study, for the latest points stated by Otmar and here are
my thoughts,
1) First of all (I think this is important), consider also the IBM JDK 9. This
page
[https://www.ibm.com/support/knowledgecenter/SSYKE2_9.0.0/com.ibm.java.multiplatform.90.doc/installing.html,]
says "Windows
The SDK is available only as part of an IBM product". Unlike Oracle's JDK 9
(which can be downloaded just like earlier versions), IBM JDK 9 (for Windows I
think) cannot be downloaded standalone. This will make it difficult to release
Xerces compatible for JDK 9 (but it should be; please read my points below),
supporting the JDKs of both IBM and Oracle.
2) It seems to me, that the modules of JDK 9 are conceptually similar to OSGi
bundles. If Xerces release does'nt consider JDK 9 modules, I think there should
be ways of converting Xerces JARs into JDK 9 modules (either via some tooling,
that convert non module JARs to the module ones – I think such tooling are
available for OSGi. Another way is to take Xerces source code, and prepare the
module JARs yourself – Xerces is open source).
In short, the Xerces deliverables we produce can be converted to JDK 9 modules
without significant problems. The question, whether we should release Xerces
JARs in near future as JDK 9 modules makes me think, it'll be too early. Also I
feel, Xerces JARs can be used in JDK 9 in a non-module way (I hope, JDK 9
hasn't broken backward compatibility of this kind).
3) I read a bit about multi-release jar. Its been introduced in JDK 9. I feel,
it'll be too early for us to use this feature. Ofcourse, people should be free
to convert Xerces source code into multi-release jars.
(all thoughts are personal)
> Remove org.w3c.dom.html.HTMLDOMImplementation from xercesImpl.jar
> -----------------------------------------------------------------
>
> Key: XERCESJ-1689
> URL: https://issues.apache.org/jira/browse/XERCESJ-1689
> Project: Xerces2-J
> Issue Type: Wish
> Components: DOM (HTML)
> Affects Versions: 2.11.0
> Reporter: Otmar Humbel
> Priority: Critical
> Fix For: 2.12.0
>
>
> The interface {{org.w3c.dom.html.HTMLDOMImplementation}} is part of the JDK
> since Java {{1.7}}.
> Java 1.7 has been EOL 'ed since a long time.
> Is there any reason to keep this interface in {{xercesImpl.jar}}? It
> produces a split package:
> {{xerces-2_11_0: jdeps --jdk-internals -cp ./xercesImpl.jar}}
> {{split package: org.w3c.dom.html [jrt:/jdk.xml.dom, ./xercesImpl.jar]}}
> which prevents people from using modules in Java {{>= 9}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
