We are in a case where we want our application to be deployed thanks to JavaWS. Our Application (the under dev JavaFX designer tool) has a dependency on the javafxpackager tool.
Currently we require the user to install the JavaFX SDK before to use the tool. This is not perfect.
We would like the SDK to be installed on the local machine when first started. The JNL Pinstaller component seems an answer to this requirement.
The scenario is has follow:
- Deploy the FX Designer Tool by loading its JNLP file (located on a server somewhere)
- Check that the Java FX SDK is installed or not. If Yes, does nothing.
- If not installed, then starts its installation.
NB: At the end of the install communicate to the Java FX Designer tool the javafx.home value.
- I currently don't see how we can communicate the javafx home value to the tool. Can we set a new parameter from a component to the main application?
Please provide your feedback to this RFE if you think that this NOT the right way to deploy the JavaFX SDK dependencies we currently have.
Thanks.
Jean-Francois Denise
Currently we require the user to install the JavaFX SDK before to use the tool. This is not perfect.
We would like the SDK to be installed on the local machine when first started. The JNL Pinstaller component seems an answer to this requirement.
The scenario is has follow:
- Deploy the FX Designer Tool by loading its JNLP file (located on a server somewhere)
- Check that the Java FX SDK is installed or not. If Yes, does nothing.
- If not installed, then starts its installation.
NB: At the end of the install communicate to the Java FX Designer tool the javafx.home value.
- I currently don't see how we can communicate the javafx home value to the tool. Can we set a new parameter from a component to the main application?
Please provide your feedback to this RFE if you think that this NOT the right way to deploy the JavaFX SDK dependencies we currently have.
Thanks.
Jean-Francois Denise