Mon premier blog

Java Deployment with JNLP and WebStart Mauro Marinilli
Publisher: Sams

Using Java Web Start ActiveX control can also be used to run a JNLP file but user interaction is required. A quick script to retrieve all the WebStart artifacts from a JNLP file and generate a corresponding classpath: #!/bin/bash. In this blog I describe how to webstart an OSGi (Equinox) based application using Eclipse as IDE. This year we've seen a number of 0 day Java exploits surfacing and various mitigating steps mentioned in various sites that could be taken to prevent us from being compromised. Now that we've covered how to build, distribute, and deploy an SWT application using Sun's Java Web Start, let's review how to implement a JNLP file. The last couple of days I went through a little nightmare: I needed to debug a Java application which showed some weird behaviour only when loaded via WebStart, but not when executed within Eclipse. Multiple internet resources told me to . The JNLP file is generated on-the-fly and downloaded to the client-machine where it uses a Cookie and the Session ID of the already-running session to re-connect to the already-running JBoss deployment. Java Web Start (henceforth, jws) provides java developers with a way to let users launch and install their applications using a URL to a Java Networking Launching Protocol (.jnlp) file (essentially some xml describing the program). Since Java 6 Update 10, Sun has distributed an NPAPI plugin and ActiveX control called "Java Deployment Toolkit" to provide developers with a simpler method of distributing their applications to end users. To exploit This Java Deployment Toolkit classid CAFEEFAC-DEC7-0000-0000-ABCDEFFEDCBA was exploited in 2010 (CVE-2010-1423). Java WebStart is a nice and easy way of deploying Java applications with one click from the web. Bash script to extract dependencies from Java WebStart.