On Thu, 20 May 2021 17:14:57 GMT, Joe Darcy <da...@openjdk.org> wrote:

> Conceptually, AccessbileObject is a sealed class with a protected constructor 
> stating
> 
>     Constructor: only used by the Java Virtual Machine.
> 
> With the language now supporting sealed classes, the AccessbileObject should 
> be marked as sealed.
> 
> Executable and Field are the subclasses of AccessbileObject in the JDK; as 
> Executable has subclasses, it is marked as non-sealed.
> 
> Please also review the corresponding CSR:
> 
> https://bugs.openjdk.java.net/browse/JDK-8224243

I think this will require reaching out to Google Guava, I think its their 
Invocable API that extends AccessibleObject outside of the JDK. We ran this 
when doing the module system where we didn't initially take into account 
sub-classes that were outside of java.base.

-------------

PR: https://git.openjdk.java.net/jdk/pull/4133

Reply via email to