JDK-8025718 : Better error messages for parsing
- Type: Bug
- Component: core-libs
- Sub-Component: java.time
- Affected Version: 8
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-10-01
- Updated: 2013-10-25
- Resolved: 2013-10-09
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 |
|---|
8 b113Fixed  |
Related Reports
|
Relates :
|
Description
Parsing originally had good error messages but some of that has been lost. When calling methods like LocalDate.parse(), the method should print the toString of the object being parsed to ensure that the internal data is visible to the user. The toString of Parsed also needs enhancing to avoid printing null if one of date or time is null. See also: https://github.com/ThreeTen/threeten/issues/342
Comments
|