Insights and updates on Java SE and OpenJDK from the Java Platform Group Product Management Team

  • March 7, 2018

The Future of JavaFX and Other Java Client Roadmap Updates

Donald Smith
Sr. Director of Product Management

[Note - a newer blog with more Roadmap information as of May 2020 can be found here - https://blogs.oracle.com/java-platform-group/java-client-roadmap-updates ]

Starting with JDK 11, Oracle is making JavaFX easier to adopt by making the technology available as a separate download, decoupled from the JDK. These changes clear the way for new contributors to engage in the open source OpenJFX community. Meanwhile, Oracle customers can benefit from continued commercial support for JavaFX in the Oracle JDK 8 through at least 2022.

JavaFX was publicly unveiled at JavaOne 2007. It was immediately compared with Adobe Flex and Microsoft Silverlight for its scripting and cross platform hardware-accelerated UI abilities.  The technology was fully open-sourced in 2011, and became part of the Oracle JDK download a year later. Under Oracle’s stewardship, it continued evolving in the OpenJDK community, attracting a passionate following of its own as a cross-platform desktop application toolkit.

JavaFX has found an audience among developers and ISVs producing unique desktop applications and solutions for specific markets blending together multimedia, web and visualization technologies. There are a number of open source libraries, frameworks and tools available to developers.

With the Java Platform Module System in place since Java SE 9, it now more viable to decouple JavaFX from the JDK, in order to make it available as a separate download.  This will make it easier for developers using JavaFX to have more freedom and flexibility with the framework.  Moreover, with our focus on increasing the release cadence of OpenJDK, JavaFX needs to be able to move forward at a pace driven by the contributions from Oracle and others in the OpenJFX community. Oracle plans to implement this decoupling starting with Java 11 (18.9 LTS). 

A few weeks ago, Oracle announced the extension of Java 8 public updates through at least January 2019 and through 2020 for personal (non-corporate) use.   More details are now available in this white paper.  The white paper also provides additional information on Applets and Web Start support on Java SE 8 as they will not be included in Java 11 (18.9 LTS).  Finally, there is more information about the road map for JavaFX Including Oracle’s plans to ship and support JavaFX in Oracle JDK 8 at least through 2022.

Developers interested in OpenJFX can subscribe to the mailing list.

Join the discussion

Comments ( 4 )
  • Patrick Thursday, March 8, 2018
    So, despite the comittment to open source that Oracle spoke about at JavaOne 2017, after reading the whitepaper I get the impression that Java WebStart is not going to be open sourced ever. Is it?
  • Alex Henry Saturday, March 10, 2018
    Hi, thanks for letting us know - this approach seems to have a bunch of really neat benefits for JavaFX development moving forward!

    However, I would like for you to make clear what Oracle's plans are when it comes to supporting and further developing JavaFX. As we know, developing and maintaining a top-notch rich-client framework that works well and seamlessly in all platforms is very hard work that only big companies like Oracle can support.

    With development being decoupled from the core Java stack, there is no guarantee that Java or OS updates won't break JavaFX in some capacity. As someone who is planning on porting an entire codebase from AWT to JavaFX, this makes me worried about what support for JavaFX will be like 5, 10 or 20 years from now.
  • Amadou DIA Sunday, March 11, 2018
    looking forward to new updates
  • Donald Smith Monday, March 12, 2018
    @Alex - at this time Oracle has stated plans to continue to support JavaFX on Java 8 through 2022, and to make it a separate module for Java 11.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.