luehe 2004/10/18 18:43:04
Modified: catalina/src/conf web.xml
Log:
Clarified description of 'reloading' init param.
I'm about to remove this param altogether, as it is redundant and
misleading (it's only evaluated in deployment mode):
reloading=true should be covered by checkInterval>0
reloading=false should be covered by checkInterval<=0
Let me know if there are any objections to removing this param and
associated APIs. This is currently only used in JspRuntimeContext to
determine whether thread for background compiles should be spawn, and may
be replaced as described above.
Revision Changes Path
1.50 +4 -1 jakarta-tomcat-catalina/catalina/src/conf/web.xml
Index: web.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/web.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- web.xml 18 Oct 2004 23:58:21 -0000 1.49
+++ web.xml 19 Oct 2004 01:43:04 -0000 1.50
@@ -160,7 +160,10 @@
<!-- trimSpaces Should white spaces in template text between -->
<!-- actions or directives be trimmed? [false] -->
<!-- -->
- <!-- reloading Should Jasper check for modified JSPs? [false] -->
+ <!-- reloading Should Jasper check for and reload modified -->
+ <!-- JSPs in deployment mode (development is set to -->
+ <!-- false)? If true, background compiles are -->
+ <!-- enabled every checkInterval seconds. [false] -->
<!-- -->
<!-- suppressSmap Should the generation of SMAP info for JSR45 -->
<!-- debugging be suppressed? [false] -->
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
