<AWT Dev> <Swing Dev> Review request #3: 6852592 (revalidate() must be smarter)

Christopher Deckers chrriis at gmail.com
Thu Jul 23 08:06:19 PDT 2009

> There's a reason to mark an Applet as a validate root: user should be able
> to call validate() on all the validate roots. If invalidate() goes up to the
> applet's parent (embedded frame), what code will call validate() on it? Do
> we want developers to write something like this:
>    applet.getParent().validate();

I remember a project where we had an Web 2.0 like page that contained
many applets. We decided to rewrite the UI framework in Swing but the
applets couldn't be migrated: applets were simple components for the
web page and became simple components of our Swing application.
Why would isValidateRoot not be coded like this for applets:
return getParent() == null? true: false;

And as to how we would validate it, if the applet contains some Swing
code, I guess users would not even notice what is happening behind the

Note that I don't particularily care about whether or not applets are
validate roots, such applet integration is not very common.


More information about the awt-dev mailing list