<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Bengt,<br>
<br>
On 12/16/14 3:12 PM, Derek White wrote:<br>
</div>
<blockquote cite="mid:54909234.9060300@oracle.com" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Bengt,<br>
<br>
On 12/16/14 6:50 AM, Bengt Rutisson wrote:<br>
</div>
<blockquote cite="mid:54901C91.7010508@oracle.com" type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
About DiagnosticMXBean. I realize that it will not be possible
to verify the "=" vs. ":=" semantics if you use the MXBean
instead of parsing the PrintFlagsFinal output. But on the other
hand I am not so sure this is an important distinction to test
as long at the values are correct. I'm fine with parsing the
output if you think this is important. The MXBean approach would
be fewer lines of code though.<br>
</blockquote>
<br>
O, I'll try MXBeans.<br>
</blockquote>
<br>
So it looks like
ManagementFactoryHelper.getDiagnosticMXBean().getVMOption() works on
the current VM? If so, I'd have to duplicate the option name and
option value in two places - in a "@run" comment and in the test
verification code. Is this right?<br>
<blockquote><tt> "@run main/othervm -XX:fisk=99" </tt><br>
<br>
<tt>...</tt><br>
<br>
<tt>String expectedValue = "99";</tt><br>
<tt>option = diagnostic.getVMOption("fisk");</tt><br>
<tt>if (!expectedValue.equals(option.getValue())) {</tt><br>
<tt> throw new RuntimeException("Wrong value for fisk. Expected
" + expectedValue + " but got " + option.getValue());</tt><br>
<tt>}</tt><br>
</blockquote>
I must be missing something.<br>
<br>
- Derek<br>
</body>
</html>