JDK-4912693 : Behavior of null arguments not specified in Java Sound
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: javax.sound
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-08-26
  • Updated: 2018-03-30
  • Resolved: 2018-03-23
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.
JDK 11
11 b07Fixed
Related Reports
CSR :  
Relates :  
Relates :  
Relates :  
Relates :  
Sub Tasks
JDK-8135100 :  
JDK-8143909 :  
Description

Name: fb126949			Date: 08/26/2003


Most Java Sound methods and constructors do not specify the behavior when passing null as one or more of the arguments.

Java API's should, however, specify explicitely what happens, if null is passed as argument.

======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon
14-06-2004

SUGGESTED FIX The suggested fix is the following: 1) Specify default behavior in package.html files Add this text to the package description of the 4 Java Sound packages: Unless otherwise noted, passing a null argument to a constructor or method in any class or interface in this package will cause a <tt>NullPointerException</tt> to be thrown. 2) Identify non-specified cases for null arguments Go through all methods and constructors and find the ones that are intended to accept a null argument. If the spec of that method/constructor does not yet state it, file a SPEC bug so that the null argument is specified in the javadoc of the method/constructor. 3) Identify/fix broken implementation Check that all methods throw a NPE when null is passed as argument and the specification of the method/constructor does not specify null as valid argument. 4) JCK tests These changes will certainly require new/updated JCK tests. Identifying broken methods/constructors in 3) could be achieved with such JCK tests.
11-06-2004

PUBLIC COMMENTS RFE: Behavior of null arguments not specified in Java Sound
10-06-2004

EVALUATION ###@###.### 2003-08-26 Important to fully specify the behavior of Java Sound methods and constructors. ###@###.### 2003-10-01 See also 4798005, which contains a list of all methods that need to be verified for such a global behavior. And 4798003.
01-10-2003