Name: mc57594 Date: 11/21/99


java version "1.3beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3beta-O)
Java(TM) HotSpot Client VM (build 1.3beta-O, mixed mode)


As Java has died as a viable content platform within the web browser
environment, we've become more interested in downloading java to the
clients. One solution is our http://www.nextbus.com/WebRun . But
that does not work for all situations, so we have a continued interest
in good java support on the client.

Unfortunately the Windows JRE 1.3beta-0 seems to be continuing the tradition of difficult and
confusion installation and execution of java content.

Us geeks might be able to figure out CLASSPATH and jar manifests, but
the rest of the world will just use windows.

Please, please, make client execution of java as easy as clicking
on a .exe file. Here are some ways that the 1.3 Early Access JRE
does not meet that standard:

1> It's own documentation link fails trying to load "/C:\Program Files\JavaSoft\JRE\1.3/Welcome.html"

2> If you launch a jar that has no manifest, no reasonable error message
is given. Either double-clicking on a jar should result in running
some java, or the user should be told what's wrong. Don't fail
silently!

3> It came with no example. Worse yet, it comes with .jar files that
don't execute.

4> The file association for ".jar" files is named strangely:
"Executable Java File"
This seems like a small thing, but every small thing is a barrier.
How abut calling it "Java Executable File", so it can be found,
and giving it a real java icon, not one of the bland windoze defaults?

5> The path inside the ".jar" association definition has
spaces, but no quotes. It is improperly formatted.

6> There is no easy default trap for exceptions. If the program gets
an exception, the screen flashes briefly (or not at all). There should
be a default handler that gives the user the information they need
(the program failed, and if you cut & paste this message the author
may be able to debug it). Don't confuse the user with the exception,
but indicate it has details as to the failure. Even better would be supporting
an email address inside the jar for automatically sending failure reports.

7> The manifest should indicate the minimum required version of java,
so a nice friendly error message can tell the user to upgrade. An
exception is a very unfriendly error message. JAVA ONLY WORKS AS
A CLIENT DISTRIBUTION METHOD IF TECHNICAL SUPPORT COSTS
ARE KEPT TO A MINIMUM!!!


Complaints about the jar utility:
---------------------------------
1> By default the jar utility should produce executable jar files.
Specifying a seperate manifest file is a pain. Make it easy, and everyone
will distribute java in jars!

2> One should be able to specify arguments when creating a jar:
Main-class: Map muni-metro.nextbus.com
(Review ID: 98060)
======================================================================