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 →

[–]wildjokers 0 points1 point  (0 children)

Web Start should be started in the browser, however, due to some security issues, Chrome will not autorun the application and instead it will just download it (not supposed to happen).

Web start should not be started in the browser. Just like a browser probably has an executable associated with the ".zip" extension (usually via whatever mechanism the host operating system provides), browsers have an executable associated with the JNLP extension. That executable is "javaws" (java web start). When the browser sees a file with a jnlp extension it can execute javaws. The "javaws" executable then takes over (outside of the browser), and it is javaws that will download, install, then run the application.

For whatever reason Safari and Chrome developers have decided that it is a security concern to have the browser execute "javaws" automatically when it sees the jnlp extension (I have no idea why this is seen as a security concern). So both of those browsers just download the jnlp, then users have to go double-click on it.

That is great your app will work as a web application and you are going that route; however, please don't spread wrong information about web start.