From - Sun May 18 10:37:15 1997
Path: world5.bellatlantic.net!out2.nntp.cais.net!news2.cais.com!in1.nntp.cais.net!hunter.premier.net!feed1.news.erols.com!disgorge.news.demon.net!demon!dispatch.news.demon.net!demon!zetnet.co.uk!not-for-mail
From: David Hopwood <hopwood@zetnet.co.uk>
Newsgroups: comp.lang.java.security
Subject: Re: JAR MANIFEST and Communicator
Date: Thu, 15 May 1997 12:39:46 +0100
Message-ID: <1997051512394674952@zetnet.co.uk>
NNTP-Posting-Host: deansgate.zetnet.co.uk
X-Mailer: ZIMACS Version 1.10 10003570
Lines: 30

In message <5ldepa$rvh1@ultra.exodus.net>
        "Tom Vaughan" <tommy@best.com> writes: 

> I have a JAR file that I've created using "jar" and signed using "javakey"
> from Sun's 1.1.1 JDK. Everything works fine using appletviewer and HotJava.
> However, Communicator complains of an "internal error - cannot parse
> manifest".

So it's a bug in either javakey or Communicator. Without more information
it's not possible to tell which (perhaps you could post the manifest file,
or put it on the web?)

> What the $#@! Is Netscape doing something in contradiction to
> Sun's specifications? What is this crap, more product differentiation?

Why the conspiracy theories? Netscape has no motive for doing this
deliberately; they were involved with designing the manifest spec (I was
one of the contributors when I was working there).

> another thing, does Communicator reconize CLASSPATH?

It did the last time I looked (in PR2). It isn't a good idea to rely on
that always being true, however. CLASSPATH is intended for applications
(and that is how most users configure it). I would much prefer that a
different setting was used for browser extensions.

David Hopwood
david.hopwood@lmh.ox.ac.uk, hopwood@zetnet.co.uk


