Building a JAR File
-
After you have created your ZIP and CAB archives, you can then create a
JAR (Java ARchive) file that will contain your compressed and archived
Applet for use with users using the most recent versions of Netscape Navigator
and HotJava.
-
Building JAR files is very similar to building TAR files that most UNIX
developers should be familiar with. Unfortunately, though, as with CABARC,
there is only a command line interface, so you need to build your JAR files
in the DOS shell using the JAR program provided with the JDK1.1.
-
The JAR program should be located in the "Bin" directory under your main
JDK directory (this is also where javac and appletviewer are located which
you should already be familiar with from earlier chapters).
-
JAR follows the generic format:
jar [command][options] jarfile [manifest file] [files]
|
Commands |
Parameter |
Comments |
t |
Used to list the contents of a jar file |
c |
Used to create a jar file. |
x |
Used to extract single or multiple files
from a jar file. |
v |
Generates verbose output to standard error |
f |
Specifies the file name of the archive |
m |
Used to include manifest information from
the given manifest file |
O |
Used for storage only. No compression
is applied and the file may be stored in your CLASSPATH |
M |
Specifies that no manifest file should
be created |
Creating a JAR File
-
To create a JAR file it is most common to use the basic form:
jar cvf JARFILENAME listoffiles
-
The "c" comand tells JAR that we are creating an archive, the "v" option
tells JAR to produce verbose information about its successes and errors,
and the "f" option specifies that we will be providing a name for the JAR
file. Unlike with CABARC, JAR will automatically recursively add any directories
which are named.
-
JAR suffers from the same problem of adding too many files to the archive
that CABARC does. Unfortunately, unlike with CABARC, we do not have an
easy way to restrict what is added without specifying every detail of the
archive. Thus, to excise the useless files from the archive, we would have
to use the following command:
jar cvf MyApplet.jar *.class Images/*.jpg Images/*.gif Utility/*.class
Listing Files in and Extracting Files From a JAR Archive
-
To list the contents of a JAR file, you will use the "t" command instead
of the "c" command. For example, the following command will list the files
that we just added to the MyApplet.jar file in the previous section:
jar tvf MyApplet.jar
-
Similarly, you can easily extract the entire contents of a JAR file using
the "x" command. For example, to extract the contents of the MyApplet.jar
file created above, you would use the following command:
jar xvf MyApplet.jar
JAR Manifests
-
The manifest file is a list of files that are to be signed that are present
within an archive. You can find out more information about them at
http://www.javasoft.com/products/jdk/1.1/docs/guide/jar/manifest.html.
Distributing JAR Archives
-
Once you have created your JAR file, you can transfer it to your web server
and reference it in the HTML file which calls your applet using the ARCHIVE
attribute of the <APPLET> tag as follows:
<APPLET CODE = "appname.class"
ARCHIVE = "jarfilename.jar"
WIDTH = "x"
HEIGHT = "y">
</APPLET>
Another interesting trick with JAR files is that you can also specify several
jar files in a comma-separated list as follows:
<APPET CODE = "my.class"
ARCHIVE = "classes.jar, graphics.jar"
WIDTH = "x"
HEIGHT = "y">
</APPLET>
As with CAB and ZIP files, the CODE attribute must still be present even
though you would jar up the class file with the rest.
Additional Resources:
Building
a Cab File
Table of Contents
Error Handling
|