On 15/06/2025 17:33, Philip Race wrote:
Perhaps these APIs should be deprecated (for removal) ?
Maybe but would require a lot of analysis to understand impact as there
are several ways to configure content handlers and there are stream
handlers that exist outside of the JDK that might interact with this.
It's also very possible that there are usages that just assume an
InputStream.
For 30 years, AudioClip has been the only public type that this API
returned for audio data.
Clearly that won't be possible after it is removed.
SoundClip is the replacement for public uses of AudioClip so it is the
obvious replacement.
And I can without too much work return a SoundClip, and that offers
the same migration path
as for direct API uses of AudioClip, so may be it is the best short
term thing, whilst a longer term
deprecation is worked out ?
A migration from AudioClip to SoundClip would require all usages to
change too. I think for now that it should be okay to just the mapping
from MultimediaContentHandlers so that it returns null.
-Alan
