a case for reconsidering JEP 398: Deprecate the Applet API for Removal
mark at lawinegevaar.nl
Tue Apr 6 09:16:43 UTC 2021
You are ignoring the core of Mark's argument. It is not about using
applets as such, but that there are unmaintained Swing applications in
the wild that are implemented both as an applet and as a normal Java
application. Removal of applet classes would therefor render those
applications inoperable, even if they are not used as applets, but as
On 2021-04-06 08:41, Remi Forax wrote:
> Hi Mark,
> As the JEP says, browsers don't support the applet API anymore,
> the plugin API has been deprecated because it lacks any sandboxing.
> Currently, the only way to see an applet is to use Internet Explorer on
> Anyway, this JEP is about tagging the Applet API with
> @Deprecated(forRemoval = true),
> so in the JDK 17, the applet API will still exist. Given that the JDK
> 17 is a LTS, a long term support release,
> you get at least 8 to 10 years of support, so you still be able to use
> applets until 2030,
> if Microsoft does not drop the support of Internet Explorer before.
> ----- Mail original -----
>> De: "mark yagnatinsky" <mark.yagnatinsky at barclays.com>
>> À: "jdk-dev" <jdk-dev at openjdk.java.net>
>> Envoyé: Jeudi 1 Avril 2021 22:49:55
>> Objet: a case for reconsidering JEP 398: Deprecate the Applet API for
>> Not sure what the proper etiquette for this list is, hope someone will
>> tell me
>> if I'm breaking any rules.
>> I'd like to make an argument against deprecating the applet API for
>> Namely, it used to be a common practice to write Swing apps in such a
>> way that
>> they can run either as an applet, or as a desktop application.
>> There are thus all sorts of nice little jars floating around the web,
>> remain perfectly usable as desktop applications today,
>> but would suddenly stop working on newer JDKs because they happen to
>> have the
>> magic words "extends Applet".
>> (For instance, this one I've used personally that would probably
>> These are often un-maintained so it's probably unrealistic to expect
>> all of them
>> to be "fixed".
>> Thus I propose that rather than removing the API's outright, one of
>> following options can be taken:
>> Option 1: do nothing: keep applets deprecated, but not for removal,
>> eventually stop testing or maintaining the relevant code.
>> Option 2: remove the bulk of the implementation, leaving just enough
>> so that
>> code that mentions the applet AIP can compile and run successfully.
>> This is a little bit tricky, in that you have to figure out what
>> counts as a
>> "workable stub".
>> For instance, the applet constructor can't be changed to
>> unconditionally throw
>> an exception since the "extends Applet" trick mentioned above results
>> in calling that constructor even when running as a desktop app.
>> That's my two cents.
>> This message is for information purposes only, it is not a
>> advice, offer or solicitation to buy or sell a product or service nor
>> official confirmation of any transaction. It is directed at persons
>> who are
>> professionals and is not intended for retail customer use. Intended
>> recipient only. This message is subject to the terms at:
>> For important disclosures, please see:
>> www.barclays.com/salesandtradingdisclaimer regarding market commentary
>> Barclays Sales and/or Trading, who are active market participants;
>> regarding our standard terms for the Investment Bank of Barclays where
>> we trade
>> with you in principal-to-principal wholesale markets transactions; and
>> respect of Barclays Research, including disclosures relating to
>> issuers, please see http://publicresearch.barclays.com.
>> If you are incorporated or operating in Australia, please see
>> important disclosure.
>> How we use personal information see our privacy notice
More information about the jdk-dev