JDK-4913027 : SPEC: several Sequencer methods should specify behaviour on closed Sequencer
  • 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-26
  • Updated: 2017-05-16
  • Resolved: 2003-10-24
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 Availabitlity Release.

To download the current JDK release, click here.
Other
5.0 b26Fixed
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
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

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

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