JavaFX-Bugs on GraalVM 19.3 (Java 11)
dlemmermann at gmail.com
Thu Nov 21 17:30:28 UTC 2019
After experimenting a lot today with the Gluon client plugin I must assume that currently not all of Java is supported via the substrate / GraalVM duo.
For example I was unable to use the java.util.Preferences API. I also got an error that said Integer.parseInt() does not exist.
Is that correct?
> On 21 Nov 2019, at 18:26, Johan Vos <johan.vos at gluonhq.com> wrote:
> We have samples showing how to build and run JavaFX applications using
> GraalVM. See our blog post  with samples .
> Keep in mind that JavaFX has some characteristics that make it non-trivial
> to apply native-image out of the box (reflection/jni configuration,
> platform-specific static libraries, including resources and bundles...).
> This is why we created Gluon Substrate , which does most of this work:
> Developers use a maven plugin  (gradle will be ready soon too) and this
> is used in the samples .
> If you use GraalVM native-image without all the parameters that Gluon
> Substrate adds, you will most likely create a "fallback-image" that still
> require a JVM and some other resources to be available at runtime, and this
> can give strange results. While I don't exclude JavaFX bugs will surface
> using this approach, I think it's more likely you're seeing issues due to
> this "mixed mode".
> - Johan
>  https://github.com/gluonhq/client-samples
>  https://github.com/gluonhq/substrate
>  https://github.com/gluonhq/client-maven-plugin
> On Wed, Nov 20, 2019 at 10:22 PM Michael Paus <mp at jugs.org> wrote:
>> I would just like to know where JavaFX problems or bugs should be reported
>> which are strictly related to running on the just released GraalVM 19.3
>> Java 11 support. Should they go into the regular JBS or should they be
>> For example: I have observed that a large JavaFX application seems to work
>> correctly at first but then suddenly all text on all controls turns
>> white and
>> white on white or light grey is not really readable anymore. I've never
>> such a behaviour on any other VM before. There is also no error message or
>> warning associated with this. It just happens.
>> There even seem to be more issues when you try to use native-image.
More information about the openjfx-dev