RFR: 8223773: DateTimeFormatter Fails to throw an Exception on Invalid CLOCK_HOUR_OF_AMPM and HOUR_OF_AMPM
Roger.Riggs at oracle.com
Thu May 30 13:50:22 UTC 2019
The behavior is within the spec and seems more just like a bug in the
Also, an exception was thrown but it was for the wrong reason.
On 05/29/2019 06:55 PM, naoto.sato at oracle.com wrote:
> Hi Joe,
> Right, I will file a corresponding CSR.
> On 5/29/19 3:51 PM, Joseph D. Darcy wrote:
>> Hi Naoto,
>> Should this bug get a CSR for the behavioral change?
>> On 5/29/2019 2:12 PM, naoto.sato at oracle.com wrote:
>>> Please review the fix for the following issue:
>>> The proposed changeset is located at:
>>> Checking the range of HourOfAmPm with the range of AmPmOfDay is
>>> apparently incorrect. Fixing it will change the behavior of parsing
>>> with SMART resolver style to throw a DateTimeParseException. This is
>>> a change in which an app will start to see an exception with
>>> incorrect data, but that is what should be in the first place.
More information about the core-libs-dev