The scripting language and mobile support have since died off and whats left are a set of welcome graphical library additions that work well with Swing and some additional deployment methods including the ability to deploy to a native app.
Having a method to bundle Java with it own private JRE is a step in the right direction but as ever it doesn't go nearly far enough or serve the complex needs of developers trying to put out usable products for demanding customers.
Having to run a build on each target platform is an unnecessary pain, updates to the app are left up to the developer to implement and the size of the executable is in many cases simply untenable (a user on StackOverflow reports their build size of 166MB, 146MB of which is the JRE - hardly streamlined).
Contrast this with JWrapper's ability to build signed iconified apps on any Java-supporting OS for all of Windows, Mac and Linux, along with auto updates, online exe's around 1MB and wealth of other features and we can see why JWrapper is gaining popularity as the JavaFX deployment solution.
Deploying JavaFX - Tweaks and Tips
Here in the real world at JWrapper we understand that deployment size is major issue for Java developers and we have worked very hard to get executables down to an absolute minimum. JWrapper does a lot of carefully designed compression automatically to your app and any bundled JRE and it also by default strips out a bunch of optional stuff in the JRE that a lot of people won't use (all within the Oracle license terms).
If you're using JavaFX then to get up and running you will want to disable this stripping to make sure JavaFX is left within the JRE you are trying to use. To turn enable this just add the NoStripJREs tag to your JWrapper XML file:
JWrapper has been architected to give you maximum flexibility during installs and updates, allowing your app to do very in-depth testing of JVMs before you accept or reject them and the whole range of Java rather than a cut-down custom scripting language to extend your installation process. It also does a bunch of wizardry to speed up the launch process for your app but in some apps with complex classloading its necessary to cut some of this out. If your JavaFX app is having any issues launching with JWrapper then adding this option to your JW XML will likely fix it:
Working round JavaFX bugs
As it turns out, JavaFX doesn't always play nice with AWT and in some cases JavaFX can hang inexplicably. One of our users pointed this out (thanks!) and also gave us a simple fix by setting a JVM option. Again a simple addition to your JWrapper XML will resolve the issue:
Instant JavaFX Deployment
If you have any issues or need any answers you can always get in touch on our Forum.