OK.
My interest is purely about any work I may need to do in this area for
jtreg.
If I recall correctly, these tests make minimal use of the actual API.
When the time comes, it may be enough to stash a private local copy of
the Applet class somewhere, and just change the imports to refer to the
new copy.
Whatever you choose to do, keep please keep me in the loop with respect
to any work that needs to be done in jtreg.
-- Jon
On 3/5/21 3:13 PM, Philip Race wrote:
I should clarify my response that there's no time frame being set here
for the actual removal
so there should be ample time to do that re-writing.
phil.
On 3/5/21 2:59 PM, Philip Race wrote:
I actually counted almost 100 such open tests. You need to remember
JApplet too.
And these open jtreg tests do not account for all of it by any means.
There are a couple of options - although I think re-writing is the
only truly viable one.
But definitely re-working all of those is one thing that has to
happen before this JEP can be integrated.
And of course submitted != targeted ..
-phil
On 3/5/21 2:37 PM, Jonathan Gibbons wrote:
On 3/5/21 2:19 PM, mark.reinh...@oracle.com wrote:
https://openjdk.java.net/jeps/398
Summary: Deprecate the Applet API for removal. It is essentially
irrelevant since all web-browser vendors have either removed
support
for Java browser plug-ins or announced plans to do so.
- Mark
I know it's not the standard browser usage, but I count 34 jtreg
tests in open/test/jdk that contain `extends Applet`.
Do you have a sense of what you want to do with jtreg GUI tests that
incidentally use Applet?
-- Jon
