Private APIs not usable in Java 9?

Robert Krüger krueger at
Thu Apr 9 05:49:42 UTC 2015

- Getting access to the native window to let our video player render into a
JFX screen, to have a video player with features and format support that
can compete with other players on the market (RT-36215), basically
following the example of Steve and Felipe's JavaOne presentation
"Integrating JavaFX with Native Technologies"
- Getting access to the currently displayed table rows by hacking into the
skin, because not being able to do so, would significantly degrade the UX
of our application (RT-39917). This will probably happen for other controls
(list, tree) in the future, when we dive in deeper because, as I understand
it, they share the same limitation.

Those two definitely so far but we have only started evaluating the porting
process and haven't had the time to check if things like RT-37372,
RT-37501, RT-40409 or RT-40379 can be worked around by using private APIs,
still hoping some of that will be fixed before we need to do something
about it ourselves.

On Wed, Apr 8, 2015 at 10:05 PM, Danno Ferrin <danno.ferrin at>

> > On Apr 8, 2015, at 1:52 PM, Robert Krüger <krueger at> wrote:
> >  our only workaround is to use private API
> For the benefit of the devs on the list, could you please point out what
> private APIs you currently need to use?  That way we can make sure proper
> JIRAs are filed and we can connect those to actual real-world problems.

Robert Krüger
Managing Partner
Lesspain GmbH & Co. KG

More information about the openjfx-dev mailing list