JDK-4909216 : Potential wrong use of Class.forName()
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.sound
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-08-19
  • Updated: 2003-08-25
  • Resolved: 2003-08-25
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.
5.0 tigerFixed
Related Reports
Relates :  
This bug is a follow-up of bug #4452022, because it hasn't been fixed completely.
For details see the bug #4452022.
The issue named there still has to be resolved for the following classes:
- com/sun/media/sound/JSSecurityManager.java
- com/sun/media/sound/NetscapeSecurity.java
- sun/audio/AudioSecurity.java
- sun/applet/AppletAudioClip.java

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b17

EVALUATION ###@###.### 2003-08-19 - NetscapeSecurity: seems obsolete; it should be removed completely. - JSSecurity: Class.foName() is used for a JMF-related hack. This hack may be obsolete. - AudioSecurity: usage of Class.forName() no longer necessary, can be removed or replaced by class literals - AppletAudioClip: not yet evaluated

PUBLIC COMMENTS Potential wrong use of Class.forName()