tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gtallen <gtal...@home.com>
Subject Re: JSP Work Directory
Date Sat, 15 Apr 2000 14:02:53 GMT
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

Mime
View raw message