Return-Path: <gtallen@home.com>
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 2518 invoked from network); 15 Apr 2000 14:02:04 -0000
Received: from ha1.rdc1.sdca.home.com (HELO mail.rdc1.sdca.home.com)
 (imail@24.0.3.66)
  by 63.211.145.10 with SMTP; 15 Apr 2000 14:02:04 -0000
Received: from home.com ([24.0.190.166]) by mail.rdc1.sdca.home.com
          (InterMail vM.4.01.02.00 201-229-116) with ESMTP
          id <20000415140045.NDUE8790.mail.rdc1.sdca.home.com@home.com>
          for <tomcat-user@jakarta.apache.org>;
          Sat, 15 Apr 2000 07:00:45 -0700
Message-ID: <38F8768D.53527972@home.com>
Date: Sat, 15 Apr 2000 07:02:53 -0700
From: gtallen <gtallen@home.com>
Reply-To: gtallen@home.com
Organization: @Home Network
X-Mailer: Mozilla 4.61 [en]C-AtHome0407  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: tomcat-user@jakarta.apache.org
Subject: Re: JSP Work Directory
References: <20000414201906.A5367@prometheus> <38F762C5.C6E5DEB8@eng.sun.com>
 <38F77B5D.EF68CF4@gefionsoftware.com>
 <000701bfa65a$040ad730$650c0a0a@insei.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: 63.211.145.10 1.6.2 0/1000/N

http://jakarta.apache.org/builds/tomcat/release/v3.1_rc1/bin

Try the latest release candidate, seems others have talked about
this but I don't recall the solution.
Greg

Josh Butikofer wrote:
> 
> I was wondering if you brilliant people out there could help me with a
> little Tomcat problem.
> 
> I am developing JSP webapps (obviously) with Tomcat 3.1 beta. I just
> downloaded it and I have been using Tomcat 3.0 and the JSWDK even before
> Tomcat. Tomcat has been excellent, for the most part, but there are two
> strange things happening:
> 
> 1 - Sometimes when I am changing JSP files, saving them, and then reloading
> the pages in my browser the Tomcat engine will recompile the JSP pages and
> then display the newly compiled stuff, no-problem. However, every once in a
> while an old version or a "ghost" version of old JSP classes will just
> happen to pop up!!! That's right! Code I worked on 3 days ago will come back
> from no where and cause all kinds of strange things to happen until I
> restart Tomcat. This happens in Tomcat 3.0 and 3.1. I do not think it is a
> browser caching problem, however I am not making any final judgements just
> yet. Just wondering if anyone out there has seen some similar behavior.
> 
> 2 - This is the REAL problem. My server.xml in the conf dir has my context
> section looking like this ( and they work fine ):
> 
> <Context path="/" docBase="C:\jswdk-1.0.1\webpages\jerky"
>             defaultSessionTimeOut="30" isWARExpanded="true"
>             isWARValidated="false" isInvokerEnabled="true"
>             isWorkDirPersistent="false">
>  </Context>
>         <Context path="/examples" docBase="examples"
>             defaultSessionTimeOut="30" isWARExpanded="true"
>             isWARValidated="false" isInvokerEnabled="true"
>             isWorkDirPersistent="false">
>  </Context>
>  <Context path="/skeleton" docBase="C:\jswdk-1.0.1\webpages\skeleton"
>             defaultSessionTimeOut="30" isWARExpanded="true"
>             isWARValidated="false" isInvokerEnabled="true"
>             isWorkDirPersistent="false">
>  </Context>
>  <Context path="/jerky" docBase="C:\jswdk-1.0.1\webpages\jerky"
>             defaultSessionTimeOut="30" isWARExpanded="true"
>             isWARValidated="false" isInvokerEnabled="true"
>             isWorkDirPersistent="false">
>   </Context>
> 
> What I need done is for the work directory to be either deleted or for the
> JSP class files to be recreated when
> I restart the Tomcat 3.1 file, regardless if the JSP files have been changed
> from the last compile or not.
> 
> Now I would assume that the isWorkDirPersistent attribute above would make
> all the
> .class and .java files in the work dir to be deleted or at least replaced
> first thing AFTER the server is restarted. I know that JSWDK and Tomcat 3.0
> would do that (after you restarted), but the new Tomcat 3.1 seems to like to
> hold onto those darn .class files and will NOT recompile them after a
> restart. What can I do, if anything, to overcome this feature/problem???? I
> would really appreciate it.
> 
> Josh
> 
> --------------------------------------------------------------------------
> To unsubscribe, email: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commmands, email: tomcat-user-help@jakarta.apache.org