🚀 go-pugleaf

Hello,

I am having a very difficult time.  I am creating a .jar file and 
placing it in my directory, but for some reason NS Commnicator 
refuses to read the latest .jar file.  It continues to read one 
from cache.


A reponse to my post on the applet newsgroup ....


> Sean C. Sheridan wrote:
> >
> > Ok,  How do I fix this?
> >
> > I had been deploying my classes by hand (cut and paste) onto my server and everything
> > was working fine.  The other day I started using the deployment wizard.  The first
> > few times everything seemed fine, and then it happened.
> >
> > For some reason I cannot view my latest deployment.  I am using Netscape Fasttrack
> > server and Netscape Communicator 4.04 + jdk patch.  I have tried Shift+reload,
> > Ctrl+reload, shift+control+reload, shift+ctrl+ alt+reload, etc. to no avail.  I have
> > shut down the server.  I have shut down Communicator.  I changed the cache settings to
> > 0 disk and 0 memory...  but it still keeps loading the 'jar' file from some magical
> > cache .... What is wrong and how do I fix it???

[Borland]
> 
> This could be tough to figure out.
> 
> Is the archive on your CLASSPATH?  I've seen instances where one has
> libraries on their CLASSPATH, and Netscape picks them up and uses them
> instead of classes from the web server.  As a result, the applet works
> one place but not another.

No,  The archive is not in my classpath, though the individual classes are in my
myclasses directory.  So, following your thoughts ... I removed all copies of the
compiled class files from my computer but, I still can't get it to work.  

Last week it was working ... compiled it deployed it ... then, one day, it just
stopped working.  (Well it actually works, just doesn't use the updated jar.)  The
only place I have a jar on my system is in the server directory tree, nowhere in any
of my classpaths do I have a jar.  Somehow it is reading from a magical cache.

And now I can't even get it to read the new jar after a computer restart.

[Borland] 
> Another thing to do would be to ensure that the JAR file you placed
> on your server is indeed the one being loaded.  Unix servers are
> case sensitive, so Foo.jar is different than Foo.JAR.

I am on a PC.  In any event, it is the only Jar on my computer.


Please help .....



Sean C. Sheridan
University of Pennsylvania
seanc@seas.upenn.edu