I am developing an application that is using some internal JDK packages
(sun.*) to work around some problems with "leaked" Swing objects that
reference my application classloader via their protection domain. This
means that my application classloader cannot be garbage collected even if
I remove a
2015/7/28 4:21 -0700, Simon Nash :
> ...
>
> With JDK 9 and Project Jigsaw, I understand that it will no longer be
> possible for my application to directly reference internal sun.* classes.
> Will it still be possible to use ClassLoader.loadClass to load these sun.*
> classes and use reflection t
2015/7/28 8:12 -0700, Simon Nash :
> mark.reinh...@oracle.com wrote:
>> 2015/7/28 4:21 -0700, Simon Nash :
>>> ...
>>>
>>> With JDK 9 and Project Jigsaw, I understand that it will no longer be
>>> possible for my application to directly reference internal sun.* classes.
>>> Will it still be possib
Is the option the Visibility Policy file?
Cheers,
Paul
On Tue, Jul 28, 2015 at 10:22 AM, wrote:
> 2015/7/28 8:12 -0700, Simon Nash :
> > mark.reinh...@oracle.com wrote:
> >> 2015/7/28 4:21 -0700, Simon Nash :
> >>> ...
> >>>
> >>> With JDK 9 and Project Jigsaw, I understand that it will no lon
mark.reinh...@oracle.com wrote:
2015/7/28 8:12 -0700, Simon Nash :
mark.reinh...@oracle.com wrote:
2015/7/28 4:21 -0700, Simon Nash :
...
With JDK 9 and Project Jigsaw, I understand that it will no longer be
possible for my application to directly reference internal sun.* classes.
Will it sti
mark.reinh...@oracle.com wrote:
2015/7/28 4:21 -0700, Simon Nash :
...
With JDK 9 and Project Jigsaw, I understand that it will no longer be
possible for my application to directly reference internal sun.* classes.
Will it still be possible to use ClassLoader.loadClass to load these sun.*
class
