> -----Original Message----- > From: jigsaw-dev [mailto:jigsaw-dev-boun...@openjdk.java.net] On Behalf Of > Alan Bateman > Sent: Wednesday, December 02, 2015 4:29 AM > To: Alan Snyder <javali...@cbfiddle.com>; jigsaw-dev > <jigsaw-dev@openjdk.java.net> > Subject: Re: A way to opt out of access restrictions on non-exported members. > > On 01/12/2015 18:15, Alan Snyder wrote: > > How is native code access to classes and methods via JNI affected by module > > encapsulation? > > > It shouldn't affect anything as these functions aren't doing access checks. > The only real change to JNI in the current prototype is the > GetModule function to get the module that a class is a member of. It's > possible that other functions may emerge in time.
So any java code can walk around module access check through native code. We can't impl the check because native code has no module information? > > -Alan
