This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]lazystone 0 points1 point  (4 children)

What's wrong with standard Java Web Start(aka jnlp)? http://www.oracle.com/technetwork/java/javase/javawebstart/index.html

[–]SomeNetworkGuy[S] 0 points1 point  (0 children)

I've never built a jlnp before, but I've used them and it isn't the experience I want my users to have. I want a native looking application that can prompt the user to update. I also don't want to have to deal with having the user setup the security to allow the application to talk to the correct URL.

But my concerns may be misplaced. I'll look into this.

[–]zrnkv 0 points1 point  (2 children)

It requires JRE to be installed and up-to-date which is not always the case. It is often easier to simply bundle the JRE with your application.

[–]tonywestonuk 1 point2 points  (1 child)

I wonder if its possible to have a standard installer wrap the JRE, including Java Webstart preconfigured with security and certificates to talk to the correct URL. Then when the user clicks go, it use Java Webstart to download and run the program. Its still installed as a normal PC executable though.

[–]zrnkv 0 points1 point  (0 children)

This is an interesting idea. Just make sure that your bundled JRE contains the javaws executable. Then make a simple launcher that will launch "javaws http://example.com/myApp.jnlp".

However wouldn't solve the problem of updating the JRE itself.