Hi Kevin, We found that simply exiting _all_ IE instances and restarting was the "quickest/easiest" way to have IE pick up new things. Its temp cache needs to disappear so the new one is grabbed from the server. Exiting IE accomplishes that. If you are talking about permanently cached cab files, then one of two actions is needed: add a #version property to the applet tag and add the same number to the signing process so the cab has it too (a higher number is needed for each version, so both need updating on each package); then each new cab is auto-downloaded and cached on page visit/refresh. or delete the cab from the permanent cab cache when a new one needs downloading; the cab stash is c:\winnt|windows\downloaded program files; the downloaded cabs have the same names as source there (no mumbo-jumbo names!). I am actually not sure what is in c:/winnt/java/packages...never had to manipulate it. Is this the temp cache maybe? > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > On Behalf > Of Kevin Esler > Sent: Friday, January 26, 2001 12:47 PM > To: [EMAIL PROTECTED] > Subject: (Slightly off topic) Edit-Build-Test cycle for Java applets > > > I'm building some Java applets for IE5. The applets need certain > privileges and hence are packaged in a signed CAB file. I test by > serving the applets up via a local Apache server. > > I've set things up so that my JDE->Build menu entry runs Gnu Make to > recompile and re-package and re-sign the CAB file. > > How does one let Internet Explorer (or Apache ?) know that the CAB > file is newer and needs to be downloaded again, after each compile > cycle ? > > I've been doing the following: > - dive down into c:/winnt/java/packages > - find the .ZIP file with the gibberish name that corresponds to my > code > - deleting it > > but this is dangerous; if you delete the wrong file by accident you > can hose IE's ability to load applets. > > Is there a better way ? > -- > Kevin Esler <[EMAIL PROTECTED]> > Boston, MA, USA. > > >
