<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 1/14/25 15:42, Ron Pressler wrote:<span style="white-space: pre-wrap">
</span></div>
<blockquote type="cite" cite="mid:58357707-AE38-4CFE-AEB0-D89F02D34A9B@oracle.com">
<pre class="moz-quote-pre" wrap="">
What I’m saying is that since you agree that granting some component the power to decide, at runtime, that strings are not immutable and that the number 5 may sometimes have the value of 6 (as that’s what opening java.base means) will still require some static configuration, then globally changing the semantics of Java code at runtime is already possible in this way via agents (<a class="moz-txt-link-freetext" href="https://docs.oracle.com/en/java/javase/23/docs/api/java.instrument/java/lang/instrument/Instrumentation.html#redefineModule(java.lang.Module,java.util.Set,java.util.Map,java.util.Map,java.util.Set,java.util.Map))">https://docs.oracle.com/en/java/javase/23/docs/api/java.instrument/java/lang/instrument/Instrumentation.html#redefineModule(java.lang.Module,java.util.Set,java.util.Map,java.util.Map,java.util.Set,java.util.Map))</a>. The JDK already supports this and so there’s no need for yet another mechanism.
— Ron</pre>
</blockquote>
<br>
Ron, thank you for your suggestion. I didn't know about it. I have
no experience working with agents, so I just read about them. Based
on what I’ve read, I’ve formed the impression that agents are not
the most suitable solution in terms of performance and flexibility
when interacting with the main application.
<p>It seems to me that using agents is the wrong direction.
Providing access to the boot layer controller appears to be a
simpler and more straightforward solution.</p>
<p>Best regards, CR<br>
</p>
</body>
</html>