I was wondering if anyone has used Java Web Start for installing the Swing client onto the users machines?
I do not know a lot about it so I was wondering if it was viable and if anyone has used it.
From what I know it means the Swing client app gets installed automatically on the users computer over the network, and any updates deployed on the server side get downloaded on the clients machine the next time they start. It is good for allowing the Swing client to be updated without needing to send updates out manually by an admin.
Is that correct? Would it be a good idea to use for our purposes?
Web Start makes updates to a federated user base easier. If you think that synchronising your travel agent clients to the latest code is a big advantage then you should certainly use it and say why you use it. I don't think anyone can fault you for that.
If you have a webstart enabled java application, then any one who wants to use a swing application need to type in the url just like a web app. The url is redirected to a jnlp file which resides in the server . For the first time the jar file for the swing app is downloaded onto ones m/c and the application comes up . From the second times onwards on typing the URL , it checks if the version of the jar file in your local m/c and server matches . If yes , the application is started from the local jar file. Only if the jar file version differs the new jar is downloaded onto your local m/c .
1. By the user has nothing do to start the new application.The webstart will help him keep updated by downloading the latest jar files. 2. The admin does not need to do anything , just that he has to put the latest jar files in the path specified in the jnlp file . 3. This download does not happen every time you start the app in ur m/c.It happens only if the jar file version differs .
Watch out for : 1. Version of the java webstart on local and the version of java used to compile the jar file. It should match.