JEP draft: Deprecate Applet APIs forRemoval
| Owner | Andy Herrick |
| Type | Feature |
| Scope | SE |
| Status | Submitted |
| Release | tbd |
| Component | client-libs / java.awt |
| Effort | S |
| Duration | S |
| Relates to | JEP 289: Deprecate the Applet API |
| Reviewed by | Alexander Matveev, Kevin Rushforth, Philip Race, Sergey Bylokhov |
| Created | 2020/11/10 15:54 |
| Updated | 2020/11/13 23:40 |
| Issue | 8256145 |
Summary
The Applet APIs were deprecated in JDK 9 (JEP 289 : https://openjdk.java.net/jeps/289)
We now intend to deprecate these APIs for removal in a future release.
Goals
-
Establish product strategy for the Applet API, marking it as legacy technology, and creating a plan for its removal from the JDK platform in a future release.
-
Identify the impact of this strategy on existing users of this API.
Motivation
The Applet API was primarily used for embedding java applets in a browser window. All browser vendors have either already removed plug-in support or else announced timelines for such removal.
Description
The following public Java SE API classes will be deprecated for removal:
- java.applet.Applet
- java.applet.AppletStub
- java.applet.AppletContext
- java.applet.AudioClip
- javax.swing.JApplet
- java.beans.AppletInitializer
Public fields, methods, and sub-classes which reference Applets in the following classes and interfaces will also have their existing deprecation annotation modified to include "forRemoval=true":
- java.beans.Beans
- javax.swing.RepaintManager
- javax.naming.Context
Classes that currently use any of the above deprecated methods or classes will have their SuppressWarnings annotation modified to include "removal".
Testing
This JEP does not add any new testing requirements.
There are hundreds of tests that need to be either modified or removed before the Applet API is removed, but this JEP is solely about deprecation. We need to examine these tests to determine if any further SuppressWarnings annotations are required.
Risks and Assumption
- There is minimal use of these APIs
- Users of these APIs can easily add SuppressWarning annotations or not compile with "-Xlint:deprecation" flag.
Impact
The impact of this deprecation may be minimal, but existing Java products use the Applet API, and we need to determine the impact of its removal before we commit to the removal.
