Recommended server for JNLP

I have never used JNLP, and I have no web/war server already running so I will install it from sratch:

Which to use?

• GlassFish
• Tomcat
• Apache
• Jetty
• Another?

I wonder if someone already using JNLP could make any recom开发者_如何学Pythonendation for the server.

I just want a blank page with a button in the middle for starting the application nothing more, nothing less.

---

If you use only JNLP you don't need Java server. JNLP is client side. Simple http server like Apache HTTP Server should be OK. HTTP server will be better solution than use of web container/Java EE server because JNLP (usually) is a static content. Even lighthttpd should be enough.

---

As already stated any server capable to serve HTTP will do. If your WebStart application is not signed by itself (i.e. you code-signed the corresponding Jar files) you could probably consider to publish the JNLP plus its resources via HTTPS. This way your clients will know that the software they are going to execute came from its rightful origin. Although unsigned WebStart applications are restricted in their privileges on the client's machine it still is a measure to elicit trust in your clients. On the other hand this requires more configuration effort with regard to the server you chose.

If your application will need some extended privileges on the client's machine such as access to the file system then I would recommend that you do sign your jar files to gain the necessary privileges automatically (don't forget to specify them in a element within your JNLP).

These are the default restrictions for unsigned WebStart apps:

• No access to local disk.
• All your jars must be downloaded from the same host. Note, however, that you can download extensions and JREs from any host as long as they are signed and trusted.
• Network connections are allowed only to host from which your jars were downloaded. ("Phone home restriction.")
• No security manager can be installed.
• No native libraries (not even in extensions).
• Limited access to system properties. (The application has read/write access to all system properties defined in the jnlp file, as well as read-only access to the same set of properties as applets

---

You dont need a server to run JNLP(Webstart).. This is how webstart works

it simply is an application that can be started over the web, this would be the procedure from the user perspective:

user goes to yourwebsite.com

user see's link: run my awesome app

user clicks link, which downloads .jnlp file

user runs the jnlp file through java web start (part of java SE, user requires java runtime environment JRE to run this)

java web start reads jnlp to get information about the server that holds the corresponding application

jar files get downloaded automatically (the first time) and then the application starts

user gets bored and closes application

the next day, user comes back and clicks your link again

application is already downloaded, so it starts right away

user gets bored again and closes your application

1 day later, you decide to update your application and you deploy the new jar file on your server, replacing one of the old files

after 2 days user clicks your link again

java web start recognizes that the user has a different version, downloads update automatically and starts the application again ... .. .