<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="MSHTML 9.00.8112.16440">
<style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;"><span style="FONT-SIZE: 10pt" dir="ltr">
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px">In the calculation of the validityDuration as seen in the example configurations:</div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px">p:validityDuration="#{1000 * 60 * 60 * 24 * 5}"
</div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"></div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"> </div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px">While the field itself is properly declared as a long in the Java class, the calculations seen above are performed as 32-bit signed integers and then cast into longs after the calculation is done. This means
that any duration over 24-25 days causes integer overflow and the code throws an exception. I tried casting the above to longs within the configuration files, but that just triggers all sorts of Spring exceptions. I'm not entirely sure where in the code the
above calcuation occurs prior to executing the actual Java class that throws the exception, but since the data type needs to be a long, it shouldn't experience 32-bit integer overflow the way it currently does.</div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"></div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"> </div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px">I am guessing a bug report should be filed, but I thought I would mention it here prior to putting in a bug report (might be a known problem internal to some Spring processing).</div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"> </div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px">Thanks,<br>
Jeff</div>
<div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"> </div>
</span></div>
</body>
</html>