JDK-4478366 : logging: logging classes should specify what happens on null args
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_7,windows_nt
  • CPU: x86,sparc
  • Submitted: 2001-07-10
  • Updated: 2001-10-08
  • Resolved: 2001-07-13
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
1.4.0 beta2Fixed
Related Reports
Duplicate :  
JDK-4432145 - java.util.logging.Logger methods: null reaction needed
Relates :  
JDK-4486754 - LOGGING APIs: Expected NullPointerException isn't thrown
Description
The java.util.logging classes should specify what happens when
null pointers are passed to methods and constructors.

This has been requested by the test team.

graham.hamilton@Eng 2001-07-10
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta2 FIXED IN: merlin-beta2 INTEGRATED IN: merlin-beta2 VERIFIED IN: merlin-beta3
14-06-2004
EVALUATION I will add some package-level javadoc comments to clarify what happens with null pointers. graham.hamilton@Eng 2001-07-10
10-07-2001