A JWS Installer for BugRunner

The JNLP Deployment File

A deployment file is written in XML and has a .jnlp extension. The file format is defined by the JNLP and API specifications (JSR-56) available from http://java.sun.com/products/javawebstart/download-spec.html. A subset is described in the developers guide in the J2SE documentation (see <JAVA_HOME>/docs/guide/jws/developersguide/contents.html).

Most JNLP files have a structure similar to Example B-1.

Example B-1. Structure of JNLP deployment file

     <?xml version="1.0" encoding="UTF-8"?>     <jnlp spec="1.0+"       codebase="http://www.foo.com/loc/"       href="appl.jnlp" >           <information> ... </information>           <security> ... </security>           <resources> ... </resources>           <application-desc> ... </application-desc>     </jnlp> 

The codebase attribute gives the base URL where this file and the other application components are stored. A file:// location may be used instead if the software is to be loaded locally. The HRef attribute gives the URL reference for this JNLP file, which can be relative to the codebase (as in Example B-1) or can be an absolute address. The information tag contains textual information about the application, utilized by JWS at retrieval and execution time. For example, references to icons and a splash screen image are placed in this element.

The security tag is optional. If present, it defines the level of increased access given to the application. Two values are possible: <all-permissions/> or the slightly less powerful <j2ee-application-client-permissions/>. They require that the application's JARs be digitally signed. The resources tag lists the JARs comprising the program. The application-desc tag states how the program is to be executed along with optional input arguments.