On 19/01/2015 12:28, Rony G. Flatscher wrote:
:
(Speculation: I would also expect that many of those will only realize the
missing of the extension
mechanism, once Java 9 gets GA and is planned to be deployed. The alternative
for those affected in
such a scenario would be to stick to their older Java deployments, if no
alternative to the
extension mechanism becomes availabel.)
The changes to deprecate this legacy mechanism are in the 8u40 EA builds
and a MR of JSR 337 is in the works with a section on deprecating this
mechanism. I'm sure there will be Oracle documentation too. One useful
command-line option in the 8u40 EA builds is
-XX:+CheckEndorsedAndExtDirs to help identify if this mechanism (or the
endorsed standards override mechanism) are being used. So lots of
preparation as we know well that removing anything has the potential to
being pain.
:
Unfortunately, this is not always the case/possible. E.g OpenOffice starts from
native code and uses
JNI to interface with Java using its own classloader that ignores the CLASSPATH
envrionment variable.
If OpenOffice is shipping with a JRE and additional scripting engines in
the ext directory then it might be a candidate to create a custom image
with the modules that it needs (including any scripting engines).
:
Where would one be able to learn (about and experiment with) what you are
creating/thinking here as
a replacement? Maybe there are some blogs sketching the ideas, possibilities?
You are on the right mailing list and I'm sure there will be lots of
discussion in time.
-Alan
