Mon premier blog

Java Deployment with JNLP and WebStart Mauro Marinilli
Publisher: Sams

Sun has used platform independence as an excuse to do nothing or rather strange things (webstart with the java control panel) for application deployment. The article starts out with a folksy portrayal of what Java Web Start (JWS) offers: Java Web Start (JWS) has always had great potential. If you have some qualms about performance, try deploying the applet using JNLP (aka WebStart). #### Java Web Start Error: #### Found unsigned entry in resource: (http://server_host:8080/plugins/scheduler/quartz.jar, 1.0) The issue is not juts with the scheduler plugin. Bash script to extract dependencies from Java WebStart. Jar -tvf WEB-INF/lib/jnlp-servlet.jar. The first one from CodeCrate Cool - cooking with gas now. To convince a user to click on a .jar instead of an .exe for installation can already be a major issue. FAIL - java.lang.ClassNotFoundException: com.sun.javaws.servlet.JnlpDownloadServlet. The good news would seem to be that of course, there a couple plugins that do neat WebStart things - including building the JNLP file from the dependencies. Follow all the instructions about deploying, etc. With 6u10 we have this idea of deploying a Java app via a packaged JNLP which you drag onto the desktop. You may get into this problem in Client after deployment. A quick script to retrieve all the WebStart artifacts from a JNLP file and generate a corresponding classpath: #!/bin/bash. If so this way to deploy is not nicely integratable with the OS preferred way to deploy applications.