<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 07/02/2024 01:56, Jiangli Zhou wrote:<br>
<blockquote type="cite" cite="mid:CALrW1jx+j34qLCNPyvDH9pcyGouDVEeMFZ76Fpt_HPzBWO1Ckw@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">I prototyped jimage included JDK resources using java.security:
<a class="moz-txt-link-freetext" href="https://github.com/openjdk/leyden/commit/b82d06c358b924bd627d07e0cd0932f5d2e7be00">https://github.com/openjdk/leyden/commit/b82d06c358b924bd627d07e0cd0932f5d2e7be00</a>
</pre>
</blockquote>
<br>
If I read this correctly, the jlink plugin copies java.security so
that that it is adjacent to java/security/Security.class. At
run-time it gets an input stream to the resource with
Security.class.getResourceAsStream. This avoids the use of jrtfs in
the previous iteration. We can go further on this. As the
bundled/default security configuration is no longer editable then
the contents are link-time are the same as run-time so the parsing
(Properties.load etc.) can be avoided. So synergy with the other
efforts here, good!<br>
<br>
-Alan<br>
</body>
</html>