Bug ID: JDK-8073218 javadoc of MessageFormat methods should specify NullPointerExceptions

Type: Bug
Component: core-libs
Sub-Component: java.text
Affected Version: 6.0,7.0.0_01,8,8u31

Priority: P4
Status: Resolved
Resolution: Duplicate
OS: windows_8
CPU: x86

Submitted: 2015-02-15
Updated: 2016-11-15
Resolved: 2016-11-15

Versions (Unresolved/Resolved/Fixed)

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.

Other
tbd_majorResolved

FULL PRODUCT VERSION :
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

A DESCRIPTION OF THE PROBLEM :
The following methods in MessageFormat should specify the behavior of passing null as parameters:

applyPattern(String pattern)
@throws NullPointerException if pattern is null

format(Object[] arguments, StringBuffer result, FieldPosition pos)
@throws NullPointerException if result is null

format(Object arguments, StringBuffer result, FieldPosition pos)
@throws NullPointerException if result is null

format(String pattern, Object... arguments)
@throws NullPointerException if any of the parameters is null



REPRODUCIBILITY :
This bug can be reproduced always.

Duplicate :	JDK-8169480 - Inconsistencies across Format class hierarchy in their API spec and actual implementation of Exceptions
Relates :	JDK-6235363 - [Fmt-*] Doc: Inconsistencies in handling of null FieldPosition in Format and subclasses