JDK-4790551 : SPEC: description of STOP event is incomplete
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.sound
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Future Project
  • OS: generic
  • CPU: generic
  • Submitted: 2002-12-09
  • Updated: 2005-05-30
  • Resolved: 2005-01-22
Related Reports
Relates :  
Relates :  
Description

Name: dkR10031			Date: 12/09/2002



The J2SE 1.4 API spec reads:

  "STOP
   public static final LineEvent.Type STOP
   A type of event that is sent when a line ceases active input or output 
   of audio data in response to a stop request, or because the end 
   of media has been reached."

However, the specification does not contain definition of the end of 
media. The condition of the STOP event generation if method stop() is
not called is ambiguous and should be defined more accurately.

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

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

EVALUATION Name: dkR10031 Date: 12/09/2002 Florian Bomers wrote: > The Stop event should generally be produced when the device goes back from running state > to Opened state. For SourceDataLines and TargetDataLines, this only happens when the > stop() method is called. Additionally, for Clip, this happens when the entire Clip is > played through and all loops are played. ====================================================================== ###@###.### 2002-12-10 As can be seen in bug 4791256 "SPEC: description of STOP event is inaccurate", I opt against using the STOP event for buffer underrun/overflow notification. So this bug should be fixed by specifying what the end of media is.
11-06-2004

PUBLIC COMMENTS SPEC: description of STOP event is incomplete
10-06-2004