<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 15.09.2023 16:59, Pedro Lamarão
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAC8PkgFTuA8RPwgjLzbcBAZA5tP2C_LJZZ+V2bfnszQ98CUaJw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">Em sex., 15 de set. de 2023 às 11:48, Rony G.
Flatscher <<a href="mailto:Rony.Flatscher@wu.ac.at"
moz-do-not-send="true" class="moz-txt-link-freetext">Rony.Flatscher@wu.ac.at</a>>
escreveu:</div>
<div dir="ltr"><br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<blockquote type="cite"> </blockquote>
<p>Actually the code already is able to configure the JVM.
However, this can be done only, if BSF4ooRexx loads the
JVM (and the environment variable
BSF4Rexx_JavaStartupOptions is set). It cannot be done
if the JVM got already loaded by someone else and the
BSF4ooRexx bridge gets loaded into the process.</p>
</div>
</blockquote>
<div><br>
</div>
<div>Whoever sets up the JVM must maintain the JVM
initialization flags.</div>
</div>
</div>
</blockquote>
<p>No, there is no *must* as so far using Java/JDK as a JRE usually
does not force any special initialization flags.<br>
</p>
<blockquote type="cite"
cite="mid:CAC8PkgFTuA8RPwgjLzbcBAZA5tP2C_LJZZ+V2bfnszQ98CUaJw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>This person must add whatever initialization flags are
appropriate and/or required whenever they become appropriate
and/or required.</div>
<div>Suppose this person assembles an application including
component XPTO, and this person desires to upgrade XPTO to
new version 123 that adds a new feature that uses the new
FFI: during this upgrade, this person also adds
--enable-native-access to the initialization flags, and all
is good. If this person is not aware of this need, it will
become aware during testing, because the JVM will alert of
this necessity.</div>
</div>
</div>
</blockquote>
<p>This is about deployment scenarios where no new applications get
created from scratch, but there are Java applications and little
Java utilitiy programs, but also native applications and little
native utilities that have been deployed with a JRE available,
possibly for many years. Take also into account that older
versions may be deployed on newer JREs and the like. This warning
aimed at application authors should never be placed in front of
(end) users.<br>
</p>
<blockquote type="cite"
cite="mid:CAC8PkgFTuA8RPwgjLzbcBAZA5tP2C_LJZZ+V2bfnszQ98CUaJw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>I cannot visualize what hypothetical situation is this in
which whoever assembles the application and sets up the JVM
is somehow incompetent or incapable to apply this change.</div>
</div>
</div>
</blockquote>
<p>Please read up the respective e-mail thread starting with Ron's
e-mail from August 21st:
<a class="moz-txt-link-rfc2396E" href="https://mail.openjdk.org/pipermail/jdk-dev/2023-August/008061.html"><https://mail.openjdk.org/pipermail/jdk-dev/2023-August/008061.html></a>.</p>
<p>---rony</p>
<p><br>
</p>
</body>
</html>