a case for reconsidering JEP 398: Deprecate the Applet API for Removal

Cay Horstmann cay.horstmann at gmail.com
Sun Apr 18 05:55:08 UTC 2021

On 16/04/2021 14:01, Mario Torre wrote:
>> On 16. Apr 2021, at 10:35, Jan Schlößin <jan at schloessin.de> wrote:
>> So we are talking about what removal means in that case. Do we have to
>> remove the class Applet or is it enough to replace all method bodies
>> with throwing UnsuportedOperationException?
> If it’s an API it needs to work. Removing is the only option.
> Cheers,
> Mario

The use case is to keep ancient apps alive that can function both as 
applets and as applications. This can be done by removing all 
functionality from the Applet classes (NOT throwing exceptions, but 
doing nothing, returning empty strings, and so on). Mostly this is 
trivial. The painful parts are AudioClip and adapting the tests.

Even though minimal, it is an engineering effort. To justify it, a 
starting point might be to collect some of those ancient apps.




Cay S. Horstmann | http://horstmann.com | mailto:cay at horstmann.com

More information about the jdk-dev mailing list