United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4913027 : SPEC: several Sequencer methods should specify behaviour on closed Sequencer

Details
Type:
Bug
Submit Date:
2003-08-26
Status:
Resolved
Updated Date:
2003-10-24
Project Name:
JDK
Resolved Date:
2003-10-24
Component:
client-libs
OS:
generic
Sub-Component:
javax.sound
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
5.0
Fixed Versions:
5.0 (b26)

Related Reports

Sub Tasks

Description
For javax.sound.midi.Sequencer, the behaviour of several methods is not specified for the case that the Sequencer is not opened:
In the current implementation, start(), stop(), startRecording() and StopRecording() throw an IllegalStateException. This seems logical and should be specified the way it is implemented.

For setSequence(InputStream) and setSequence(Sequence), an IllegalStateException is thrown, too. However, it should be possible to set a Sequence even on a closed Sequencer. This should be specified explicitely, and the implementation changed.

For getSequence(), no exception is thrown. This is considered correct. However, it should be specified explicitly that this call is legal even on a closed Sequencer.

                                    

Comments
PUBLIC COMMENTS

SPEC: several Sequencer methods should specify behaviour on closed Sequencer
                                     
2004-06-10
EVALUATION

Bug verified. While most of the work required is changing the specification, modifying setSequence() requires coding work.
                                     
2004-06-11
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
tiger
tiger-beta

FIXED IN:
tiger-beta

INTEGRATED IN:
tiger-b26
tiger-beta


                                     
2004-06-14



Hardware and Software, Engineered to Work Together