[LANG-1121] FastDateFormat.parse() does not handle wrong length string

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 3.3.2
• Component/s: lang.time.*
• Assignee: Charles Honton
• Reporter: Henry Kang
• Created: 29/Apr/15 04:57
• Updated: 19/Oct/16 15:24
• Resolved: 30/Apr/15 16:18

Description

FDFP does not handled wrong length string.

for example,

// Wed Apr 29 00:00:00 KST 2015
FastDateFormat.getInstance("yyyyMMdd").parse("20150429");
// throws ParseException
FastDateFormat.getInstance("yyyyMMdd").parse("2015");
// Thu Mar 16 00:00:00 KST 81724
FastDateFormat.getInstance("yyyyMMdd").parse("20150429113100");

I think result of third throws ParseException,
but FastDateFormat.parse() returns wrong year, ex, 81724 instead of 2015.

As I tested,
regex.matcher.group => (2015)(04)(29113100) => setCalendar => March 16, 81724