<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<pre>This looks fine to me.
Mandy
</pre>
<br>
<div class="moz-cite-prefix">On 2/5/18 11:26 AM, Adam Petcher wrote:<br>
</div>
<blockquote type="cite"
cite="mid:98dcebbb-545e-0e6f-c21c-4b31a081553d@oracle.com">Please
review the following change:
<br>
<br>
JBS: <a class="moz-txt-link-freetext" href="https://bugs.openjdk.java.net/browse/JDK-8194251">https://bugs.openjdk.java.net/browse/JDK-8194251</a>
<br>
Webrev: <a class="moz-txt-link-freetext" href="http://cr.openjdk.java.net/~apetcher/8194251/webrev.00/">http://cr.openjdk.java.net/~apetcher/8194251/webrev.00/</a>
<br>
<br>
We ran into a problem related to loading locale data when a
security policy file is malformed. The parse error is localized
and printed, which requires the locale data to be loaded, which
triggers a security policy check, which results in deadlock or
infinite recursion.
<br>
<br>
This change removes localization from all messages during policy
file parsing and loading. I believe that this behavior is
acceptable according to our localization requirements. I removed
the code that tried to determine whether localization would
succeed, because making it work reliably would be difficult. Now
the client of LocalizedMessage will need to explicitly state
whether the message should be localized or not.
<br>
<br>
</blockquote>
<br>
</body>
</html>