Deployment

[Tom Eugelink]

As describe in a previous mail, I would go for a layered approach similar to WAR files:

- A single WAR-alike format which contains all files that are needed; jars, resources, etc.
   * distribution is done by simply copying it
   * cross platform

- That WAR file can easily be wrapped in an exe for Windows or Mac that only needs to find the JRE to run the WAR with, or actually include the JRE (since it now it no longer cross platform).
   * distribution is done by simply copying it

- And that can easily be wrapped in a standard installer.
   * This would mean nothing more that creating uninstaller records within the OS.
   * requires install rights on the OS

This is identical to the problems with a Swing application, not JavaFX specific.

I'm all enterpricy so appstores are not in my scope, but easily deployment (aka copy) is. Right now my "app jar" solution unpacks it all to a temp dir and then starts a second VM, while the first goes into a monitoring state.

Tom




On 2012-04-20 08:32, Igor Nekrestyanov wrote:
> On 4/19/12 11:03 PM, Tom Eugelink wrote:
>>
>> Ok. How about the "there is no standard way to distribute a stand alone JavaFX application"? Create a JIRA issue?
> Could you please be more specific?
>
> What is "standard way" and how do you expect to distribute this package?
> Is it different problem from distributing java application (especially once javafx runtime will be part of the JRE)?
> Do you expect to application "install" on the user system or run from the package?
> Are you thinking about shipping your application to the App Store?
>
> We might have related feature request already:
>    http://javafx-jira.kenai.com/browse/RT-19446
>       "Add ability to co-bundle Java + JavaFX + App into a single native executable"
>
> It is on 2.2 list right now but it is not clear if we can support other native packages for platforms other than Mac yet
> (see discussion in the JIRA).
>
> -igor
>
>