cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-10-26 Thread remm
remm2004/10/26 05:33:22

  Modified:webapps/docs/config context.xml
  Log:
  - Clarify wording.
  
  Revision  ChangesPath
  1.18  +3 -2  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- context.xml   5 Oct 2004 17:12:52 -   1.17
  +++ context.xml   26 Oct 2004 12:33:22 -  1.18
  @@ -168,8 +168,9 @@
   If you specify a context path of an empty string (), you are
   defining the emdefault/em web application for this Host, which
   will process all requests not assigned to other Contexts. The value of
  -this field must not be set most of the time, as it will be infered from
  -the filenames used for either the .xml context file of the docBase./p
  +this field must not be set except when statically defining a Context in
  +server.xml, as it will be infered from the filenames used for either the 
  +.xml context file or the docBase./p
 /attribute
   
 attribute name=reloadable required=false
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-10-18 Thread yoavs
yoavs   2004/10/18 10:30:25

  Modified:webapps/docs/config Tag: TOMCAT_5_0 context.xml
  Log:
  Typo fix.
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.10.2.2  +2 -2  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.10.2.1
  retrieving revision 1.10.2.2
  diff -u -r1.10.2.1 -r1.10.2.2
  --- context.xml   31 Aug 2004 14:50:41 -  1.10.2.1
  +++ context.xml   18 Oct 2004 17:30:25 -  1.10.2.2
  @@ -259,7 +259,7 @@
   of the flag is codefalse/code./p
 /attribute
   
  -  attribute value=tldNamespaceAware required=false
  +  attribute name=tldNamespaceAware required=false
   pIf the value of this flag is codetrue/code, the TLD files
   XML validation will be namespace-aware.  If you turn this flag on,
   you should probably also turn codetldValidation/code on.  The
  @@ -268,7 +268,7 @@
   /p
 /attribute
   
  -  attribute value=tldValidation required=false
  +  attribute name=tldValidation required=false
   pIf the value of this flag is codetrue/code, the TLD files
   will be XML validated on context startup.  The default value for
   this flag is codefalse/code, and setting it to true will incur
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread yoavs
yoavs   2004/08/31 07:41:48

  Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
   webapps/docs/config context.xml
  Log:
  - Made TLD processing optional (default is true for backward compatability and it's 
the more common case anyways).
  - Documented new processTlds context attribute as well as tldValidation and 
tldNamespaceAware context attributes.
  
  Revision  ChangesPath
  1.143 +59 -30
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java
  
  Index: StandardContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
  retrieving revision 1.142
  retrieving revision 1.143
  diff -u -r1.142 -r1.143
  --- StandardContext.java  29 Aug 2004 16:46:09 -  1.142
  +++ StandardContext.java  31 Aug 2004 14:41:47 -  1.143
  @@ -613,6 +613,10 @@
*/
private boolean webXmlNamespaceAware = false;
   
  +/**
  + * Attribute value used to turn on/off TLD processing
  + */
  +private boolean processTlds = true;
   
   /**
* Attribute value used to turn on/off XML validation
  @@ -4026,37 +4030,13 @@
   
   // Start the Valves in our pipeline (including the basic),
   // if any
  -if (pipeline instanceof Lifecycle)
  +if (pipeline instanceof Lifecycle) {
   ((Lifecycle) pipeline).start();
  + }
   
  -// Read tldListeners. XXX Option to disable
  -TldConfig tldConfig = new TldConfig();
  -tldConfig.setContext(this);
  -
  -// (1)  check if the attribute has been defined
  -//  on the context element.
  -tldConfig.setTldValidation(tldValidation);
  -tldConfig.setTldNamespaceAware(tldNamespaceAware);
  -
  -// (2) if the attribute wasn't defined on the context
  -// try the host.
  -if (!tldValidation){
  -tldConfig.setTldValidation
  -(((StandardHost) getParent()).getXmlValidation());
  -}
  -
  -if (!tldNamespaceAware){
  -tldConfig.setTldNamespaceAware
  -(((StandardHost) getParent()).getXmlNamespaceAware());
  -}
  -
  -try {
  -tldConfig.execute();
  -} catch (Exception ex) {
  -log.error(Error reading tld listeners  
  -  + ex.toString(), ex);
  -//ok=false;
  -}
  +if(getProcessTlds() {
  + processTlds();
  + }
   
   // Notify our interested LifecycleListeners
   lifecycle.fireLifecycleEvent(START_EVENT, null);
  @@ -4173,6 +4153,40 @@
   
   //cacheContext();
   }
  +
  +/**
  + * Processes TLDs.
  + *
  + * @throws LifecycleException If an error occurs
  + */
  + protected void processTlds() throws LifecycleException {
  +   TldConfig tldConfig = new TldConfig();
  +   tldConfig.setContext(this);
  +
  +   // (1)  check if the attribute has been defined
  +   //  on the context element.
  +   tldConfig.setTldValidation(tldValidation);
  +   tldConfig.setTldNamespaceAware(tldNamespaceAware);
  +
  +   // (2) if the attribute wasn't defined on the context
  +   // try the host.
  +   if (!tldValidation) {
  + tldConfig.setTldValidation
  +   (((StandardHost) getParent()).getXmlValidation());
  +   }
  +
  +   if (!tldNamespaceAware) {
  + tldConfig.setTldNamespaceAware
  +   (((StandardHost) getParent()).getXmlNamespaceAware());
  +   }
  +
  +   try {
  + tldConfig.execute();
  +   } catch (Exception ex) {
  + log.error(Error reading tld listeners  
  ++ ex.toString(), ex); 
  +   }
  + }
   
   private void cacheContext() {
   try {
  @@ -5288,6 +5302,21 @@
   return tldValidation;
   }
   
  +/**
  + * Sets the process TLDs attribute.
  + *
  + * @param newProcessTlds The new value
  + */
  +public void setProcessTlds(boolean newProcessTlds) {
  + processTlds = newProcessTlds;
  +}
  +
  +/**
  + * Returns the processTlds attribute value.
  + */
  +public boolean getProcessTlds() {
  + return processTlds;
  +}
   
   /**
* Get the server.xml host attribute's xmlNamespaceAware.
  
  
  
  1.12  +22 -0 jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: 

cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread yoavs
yoavs   2004/08/31 07:50:41

  Modified:catalina/src/share/org/apache/catalina/core Tag: TOMCAT_5_0
StandardContext.java
   webapps/docs Tag: TOMCAT_5_0 changelog.xml
   webapps/docs/config Tag: TOMCAT_5_0 context.xml
  Log:
  Added StandardContext processTlds attribute, added context configuration references 
docs for processTlds, tldValidation, tldNamespaceAware.
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.130.2.3 +60 -30
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java
  
  Index: StandardContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
  retrieving revision 1.130.2.2
  retrieving revision 1.130.2.3
  diff -u -r1.130.2.2 -r1.130.2.3
  --- StandardContext.java  28 Aug 2004 23:57:02 -  1.130.2.2
  +++ StandardContext.java  31 Aug 2004 14:50:41 -  1.130.2.3
  @@ -602,6 +602,10 @@
*/
private boolean webXmlNamespaceAware = false;
   
  +/**
  + * Attribute value used to turn on/off TLD processing
  + */
  +private boolean processTlds = true;
   
   /**
* Attribute value used to turn on/off XML validation
  @@ -4254,37 +4258,13 @@
   
   // Start the Valves in our pipeline (including the basic),
   // if any
  -if (pipeline instanceof Lifecycle)
  +if (pipeline instanceof Lifecycle) {
   ((Lifecycle) pipeline).start();
  + }
   
  -// Read tldListeners. XXX Option to disable
  -TldConfig tldConfig = new TldConfig();
  -tldConfig.setContext(this);
  -
  -// (1)  check if the attribute has been defined
  -//  on the context element.
  -tldConfig.setTldValidation(tldValidation);
  -tldConfig.setTldNamespaceAware(tldNamespaceAware);
  -
  -// (2) if the attribute wasn't defined on the context
  -// try the host.
  -if (!tldValidation){
  -tldConfig.setTldValidation
  -(((StandardHost) getParent()).getXmlValidation());
  -}
  -
  -if (!tldNamespaceAware){
  -tldConfig.setTldNamespaceAware
  -(((StandardHost) getParent()).getXmlNamespaceAware());
  -}
  -
  -try {
  -tldConfig.execute();
  -} catch (Exception ex) {
  -log.error(Error reading tld listeners  
  -  + ex.toString(), ex);
  -//ok=false;
  -}
  +if(getProcessTlds() {
  + processTlds();
  + }
   
   // Notify our interested LifecycleListeners
   lifecycle.fireLifecycleEvent(START_EVENT, null);
  @@ -4401,6 +4381,41 @@
   
   //cacheContext();
   }
  +
  +   /**
  +* Processes the TLDs.
  +*
  +* @throws LifecycleException If an error occurs
  +*/
  +protected void processTlds() throws LifecycleException {
  +  TldConfig tldConfig = new TldConfig();
  +  tldConfig.setContext(this);
  +
  +  // (1)  check if the attribute has been defined
  +  //  on the context element.
  +  tldConfig.setTldValidation(tldValidation);
  +  tldConfig.setTldNamespaceAware(tldNamespaceAware);
  +
  +  // (2) if the attribute wasn't defined on the context
  +  // try the host.
  +  if (!tldValidation){
  +tldConfig.setTldValidation
  +  (((StandardHost) getParent()).getXmlValidation());
  +  }
  +
  +  if (!tldNamespaceAware){
  +tldConfig.setTldNamespaceAware
  +  (((StandardHost) getParent()).getXmlNamespaceAware());
  +  }
  +
  +  try {
  +tldConfig.execute();
  +  } catch (Exception ex) {
  +log.error(Error reading tld listeners  
  +  + ex.toString(), ex);
  +  }
  +}
  +
   
   private void cacheContext() {
   try {
  @@ -5586,7 +5601,22 @@
   public boolean getTldValidation(){
   return tldValidation;
   }
  +   
  +/**
  + * Sets the processTlds attribute value.
  + *
  + * @param newProcessTlds The new attribute value
  + */
  +public void setProcessTlds(boolean newProcessTlds) {
  + processTlds = newProcessTlds;
  +}
   
  +/**
  + * Returns the processTlds attribute value.
  + */
  +public boolean getProcessTlds() {
  + return processTlds;
  +}
   
   /**
* Get the server.xml host attribute's 

Re: cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread Remy Maucherat
[EMAIL PROTECTED] wrote:
yoavs   2004/08/31 07:50:41
 Modified:catalina/src/share/org/apache/catalina/core Tag: TOMCAT_5_0
   StandardContext.java
  webapps/docs Tag: TOMCAT_5_0 changelog.xml
  webapps/docs/config Tag: TOMCAT_5_0 context.xml
 Log:
 Added StandardContext processTlds attribute, added context configuration references docs for processTlds, tldValidation, tldNamespaceAware.
 

I can feel two more commits are coming in shortly ;)
Can you fix the tabs at the same time ?
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread Shapira, Yoav

Hi,
I'm actually working in emacs over PuTTY due to some weird network/firewall 
(mis)configuration issues here at work, so it's a pain for me to fix the tabs at this 
time ;(

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 10:53 AM
To: Tomcat Developers List
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs/config
context.xml

[EMAIL PROTECTED] wrote:

yoavs   2004/08/31 07:50:41

  Modified:catalina/src/share/org/apache/catalina/core Tag: TOMCAT_5_0
StandardContext.java
   webapps/docs Tag: TOMCAT_5_0 changelog.xml
   webapps/docs/config Tag: TOMCAT_5_0 context.xml
  Log:
  Added StandardContext processTlds attribute, added context configuration
references docs for processTlds, tldValidation, tldNamespaceAware.


I can feel two more commits are coming in shortly ;)
Can you fix the tabs at the same time ?

Rémy


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread Paul Speed
To configure space tabs on Emacs... quoted from:
http://www.student.northpark.edu/pemente/emacs_tabs.htm
 For this session, force Emacs to indent with spaces, never with TABs:

 M-x set-variableRET indent-tabs-modeRET nil

 Permanently force Emacs to indent with spaces, never with TABs:

 (setq-default indent-tabs-mode nil);   # put this in your .emacs file
Or, to just one spot convert tabs to spaces for a given selection:
M-x untabify
I don't have an emacs up and running at the moment so can't verify, but 
it sounds right from what I remember.  As I recall, untabify requires 
selecting the contents of the buffer first.

-Paul
Shapira, Yoav wrote:
Hi,
I'm actually working in emacs over PuTTY due to some weird network/firewall 
(mis)configuration issues here at work, so it's a pain for me to fix the tabs at this 
time ;(
Yoav Shapira
Millennium Research Informatics

-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 10:53 AM
To: Tomcat Developers List
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs/config
context.xml
[EMAIL PROTECTED] wrote:

yoavs   2004/08/31 07:50:41
Modified:catalina/src/share/org/apache/catalina/core Tag: TOMCAT_5_0
  StandardContext.java
 webapps/docs Tag: TOMCAT_5_0 changelog.xml
 webapps/docs/config Tag: TOMCAT_5_0 context.xml
Log:
Added StandardContext processTlds attribute, added context configuration
references docs for processTlds, tldValidation, tldNamespaceAware.

I can feel two more commits are coming in shortly ;)
Can you fix the tabs at the same time ?
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This e-mail, including any attachments, is a confidential business communication, 
and may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread Shapira, Yoav

Hi,
Good tip, done, thanks.

I was going to raise the issue of Jalopy-fying Tomcat 5.5 anyways.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Paul Speed [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 1:18 PM
To: Tomcat Developers List
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs/config
context.xml


To configure space tabs on Emacs... quoted from:
http://www.student.northpark.edu/pemente/emacs_tabs.htm

  For this session, force Emacs to indent with spaces, never with TABs:
 
  M-x set-variableRET indent-tabs-modeRET nil
 
  Permanently force Emacs to indent with spaces, never with TABs:
 
  (setq-default indent-tabs-mode nil);   # put this in your .emacs file

Or, to just one spot convert tabs to spaces for a given selection:

M-x untabify

I don't have an emacs up and running at the moment so can't verify, but
it sounds right from what I remember.  As I recall, untabify requires
selecting the contents of the buffer first.

-Paul

Shapira, Yoav wrote:

 Hi,
 I'm actually working in emacs over PuTTY due to some weird
network/firewall (mis)configuration issues here at work, so it's a pain for
me to fix the tabs at this time ;(

 Yoav Shapira
 Millennium Research Informatics



-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 10:53 AM
To: Tomcat Developers List
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs/config
context.xml

[EMAIL PROTECTED] wrote:


yoavs   2004/08/31 07:50:41

 Modified:catalina/src/share/org/apache/catalina/core Tag:
TOMCAT_5_0
   StandardContext.java
  webapps/docs Tag: TOMCAT_5_0 changelog.xml
  webapps/docs/config Tag: TOMCAT_5_0 context.xml
 Log:
 Added StandardContext processTlds attribute, added context
configuration

references docs for processTlds, tldValidation, tldNamespaceAware.


I can feel two more commits are coming in shortly ;)
Can you fix the tabs at the same time ?

Rémy


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





 This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged.  This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else.  If you are not the(an) intended
recipient, please immediately delete this e-mail from your computer system
and notify the sender.  Thank you.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-08-31 Thread yoavs
yoavs   2004/08/31 12:55:17

  Modified:webapps/docs status.xml
   webapps/docs/config context.xml
  Log:
  Cleaned up status and correct the XML for tld validation attributes.
  
  Revision  ChangesPath
  1.7   +11 -9 jakarta-tomcat-catalina/webapps/docs/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/status.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- status.xml5 Aug 2004 13:10:35 -   1.6
  +++ status.xml31 Aug 2004 19:55:17 -  1.7
  @@ -30,21 +30,18 @@
 section name=Current Status Summary
   p
 bTomcat 5.0.27/b was released on June 17th, 2004.  At that time, the 
TOMCAT_5_0
  -  branch was tagged in CVS, and work on Tomcat 5.1 (or 5.5, or 5.next, we 
haven't
  -  decided yet) began.  Until the first stable release of Tomcat 5.1, building 
from
  +  branch was tagged in CVS, and work on Tomcat 5.5 began.  Until the first 
stable 
  +  release of Tomcat 5.1, building from
 CVS head may be unstable or broken: use the TOMCAT_5_0 branch tag to build
 the Tomcat 5.0 releases.
   /p
   p
  -  bTomcat 5.1/b has several major goals.  They are discussed in the 
tomcat-dev
  +  bTomcat 5.5/b has several major goals.  They are discussed in the 
tomcat-dev
 mailing list's 5.next thread: 
 a 
href=http://marc.theaimsgroup.com/?l=tomcat-devamp;w=2amp;r=1amp;s=5.nextamp;q=b;MARC/a.
  -  The status of some of these items is detailed below.
  -/p
  -p
  -  bTomcat 4.0.x/b is relatively old, and not actively maintained or 
supported.
  -  It is strongly recommended that users of these releases upgrade to the latest
  -  stable Tomcat 5.0 release or at least the latest stable Tomcat 4.1 release.
  +  The status of some of these items is detailed below.  Once 5.5 releases are
  +  available, please refer to the Changelog accompanying each release for 
detailed
  +  changes, enhancements, and fixes.
   /p
   p
 bTomcat 4.1.x/b is no longer actively developed.  It is maintained to 
address
  @@ -52,6 +49,11 @@
 for Tomcat 4.1.x will likely cease once a stable release or two of Tomcat 5.1 
are out.
 Users of Tomcat 4.1.x are strongly encouraged to upgrade to the latest stable 
Tomcat
 5.0 release.
  +/p
  +p
  +  bTomcat 4.0.x/b is relatively old, and not actively maintained or 
supported.
  +  It is strongly recommended that users of these releases upgrade to the latest
  +  stable Tomcat 5.0 release or at least the latest stable Tomcat 4.1 release.
   /p
   p
 bTomcat 3.3.x/b is in roughly the same maintenance mode as Tomcat 4.1.x.
  
  
  
  1.13  +2 -2  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- context.xml   31 Aug 2004 14:41:48 -  1.12
  +++ context.xml   31 Aug 2004 19:55:17 -  1.13
  @@ -277,7 +277,7 @@
   of the flag is codefalse/code./p
 /attribute
   
  -  attribute value=tldNamespaceAware required=false
  +  attribute name=tldNamespaceAware required=false
   pIf the value of this flag is codetrue/code, the TLD files
   XML validation will be namespace-aware.  If you turn this flag on,
   you should probably also turn codetldValidation/code on.  The
  @@ -286,7 +286,7 @@
   /p
 /attribute
   
  -  attribute value=tldValidation required=false
  +  attribute name=tldValidation required=false
   pIf the value of this flag is codetrue/code, the TLD files
   will be XML validated on context startup.  The default value for
   this flag is codefalse/code, and setting it to true will incur
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-06-02 Thread yoavs
yoavs   2004/06/02 05:43:34

  Modified:webapps/docs/config context.xml
  Log:
  Added default info for reloadable attribute.
  
  Revision  ChangesPath
  1.10  +2 -1  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- context.xml   6 Feb 2004 14:26:10 -   1.9
  +++ context.xml   2 Jun 2004 12:43:34 -   1.10
  @@ -165,7 +165,8 @@
   changes, and automatically reload the web application if a change
   is detected.  This feature is very useful during application
   development, but it requires significant runtime overhead and is
  -not recommended for use on deployed production applications.  You
  +not recommended for use on deployed production applications.  That's
  +why the default setting for this attribute is ifalse/i.  You
   can use the a href=../manager-howto.htmlManager/a web
   application, however, to trigger reloads of deployed applications
   on demand./p
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-02-06 Thread yoavs
yoavs   2004/02/06 06:26:10

  Modified:webapps/docs/config context.xml
  Log:
  Corrected typo.
  
  Revision  ChangesPath
  1.9   +3 -1  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- context.xml   5 Feb 2004 23:17:21 -   1.8
  +++ context.xml   6 Feb 2004 14:26:10 -   1.9
  @@ -53,7 +53,9 @@
 reconfiguration of the web application, since the main 
 codeconf/server.xml/code file cannot be reloaded without restarting
 Tomcat. bPlease note that for tomcat 5.x, unlike tomcat 4.x, it is NOT
  -  recommended to place lt;Contextgt; elements directory in the server.xml 
file./b
  +  recommended to place lt;Contextgt; elements directly in the server.xml file./b
  +  Instead, put them in the META-INF/context.xml directory of your WAR file or
  +  the conf directory as described above.
 /p
   
 pIn addition to explicitly specified Context elements, there are
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-02-05 Thread yoavs
yoavs   2004/02/05 08:19:36

  Modified:webapps/docs/config context.xml
  Log:
  Added note about NOT placing context elements in server.xml
  
  Revision  ChangesPath
  1.7   +4 -3  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- context.xml   30 Nov 2003 14:35:45 -  1.6
  +++ context.xml   5 Feb 2004 16:19:36 -   1.7
  @@ -37,8 +37,7 @@
 directory hierarchy)./p
   
 pYou may define as many strongContext/strong elements as you
  -  wish, nested within a a href=host.htmlHost/a element in
  -  codeconf/server.xml/code.  Each such Context MUST have a unique
  +  wish.  Each such Context MUST have a unique
 context path, which is defined by the codepath/code attribute.
 In addition, you MUST define a Context with a context path equal to
 a zero-length string.  This Context becomes the emdefault/em
  @@ -53,7 +52,9 @@
 Application Deployment/a for more information. This method allows dynamic
 reconfiguration of the web application, since the main 
 codeconf/server.xml/code file cannot be reloaded without restarting
  -  Tomcat./p
  +  Tomcat. bPlease note that for tomcat 5.x, unlike tomcat 4.x, it is NOT
  +  recommended to place Context elements directory in the server.xml file./b
  +  /p
   
 pIn addition to explicitly specified Context elements, there are
 several techniques by which Context elements can be created automatically
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml

2004-02-05 Thread fhanik
fhanik  2004/02/05 15:17:21

  Modified:webapps/docs/config context.xml
  Log:
  fixed the xml
  
  Revision  ChangesPath
  1.8   +1 -1  jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- context.xml   5 Feb 2004 16:19:36 -   1.7
  +++ context.xml   5 Feb 2004 23:17:21 -   1.8
  @@ -53,7 +53,7 @@
 reconfiguration of the web application, since the main 
 codeconf/server.xml/code file cannot be reloaded without restarting
 Tomcat. bPlease note that for tomcat 5.x, unlike tomcat 4.x, it is NOT
  -  recommended to place Context elements directory in the server.xml file./b
  +  recommended to place lt;Contextgt; elements directory in the server.xml 
file./b
 /p
   
 pIn addition to explicitly specified Context elements, there are
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml defaultcontext.xml resources.xml

2003-11-30 Thread remm
remm2003/11/30 06:35:45

  Modified:webapps/docs/config context.xml defaultcontext.xml
resources.xml
  Log:
  - Documentation on the various flags which were added.
  - Add big warnings about the flags which are dangerous in Windows.
  
  Revision  ChangesPath
  1.6   +47 -0 jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- context.xml   30 Jul 2003 18:37:51 -  1.5
  +++ context.xml   30 Nov 2003 14:35:45 -  1.6
  @@ -188,11 +188,58 @@
   
   attributes
   
  +  attribute name=allowLinking required=false
  +pIf the value of this flag is codetrue/code, symlinks will be
  +allowed inside the web application, pointing to resources outside the
  +web application base path. If not specified, the default value
  +of the flag is codefalse/code./p
  +pbNOTE: This flag MUST NOT be set to true on the Windows platform
  +(or any other OS which does not have a case sensitive filesystem),
  +as it will disable case sensitivity checks, allowing JSP source code
  +disclosure, among other security problems./b/p
  +  /attribute
  +
  +  attribute name=cacheMaxSize required=false
  +pMaximum size of the static resource cache in kilobytes. 
  +If not specified, the default value is code10240/code
  +(10 megabytes)./p
  +  /attribute
  +
  +  attribute name=cacheTTL required=false
  +pAmount of time in milliseconds between cache entries revalidation.
  +If not specified, the default value is code5000/code 
  +(5 seconds)./p
  +  /attribute
  +
  +  attribute name=cachingAllowed required=false
  +pIf the value of this flag is codetrue/code, the cache for static
  +resources will be used. If not specified, the default value
  +of the flag is codetrue/code./p
  +  /attribute
  +
  +  attribute name=caseSensitive required=false
  +pIf the value of this flag is codetrue/code, all case sensitivity
  +checks will be disabled. If not 
  +specified, the default value of the flag is codetrue/code./p
  +pbNOTE: This flag MUST NOT be set to false on the Windows platform
  +(or any other OS which does not have a case sensitive filesystem),
  +as it will disable case sensitivity checks, allowing JSP source code
  +disclosure, among other security problems./b/p
  +  /attribute
  +
 attribute name=debug required=false
   pThe level of debugging detail logged by this strongEngine/strong
   to the associated a href=logger.htmlLogger/a.  Higher numbers
   generate more detailed output.  If not specified, the default
   debugging detail level is zero (0)./p
  +  /attribute
  +
  +  attribute name=managerChecksFrequency required=false
  +pFrequency of the session expiration, and related manager operations.
  +Manager operations will be done once for the specified amount of
  +backgrondProcess calls (ie, the lower the amount, the most often the
  +checks will occur). The minimum value is 1, and the default value is 6.
  +/p
 /attribute
   
 attribute name=swallowOutput required=false
  
  
  
  1.6   +17 -2 jakarta-tomcat-catalina/webapps/docs/config/defaultcontext.xml
  
  Index: defaultcontext.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/defaultcontext.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- defaultcontext.xml15 Nov 2003 09:45:35 -  1.5
  +++ defaultcontext.xml30 Nov 2003 14:35:45 -  1.6
  @@ -96,6 +96,10 @@
   allowed inside the web application, pointing to resources outside the
   web application base path. If not specified, the default value
   of the flag is codefalse/code./p
  +pbNOTE: This flag MUST NOT be set to true on the Windows platform
  +(or any other OS which does not have a case sensitive filesystem),
  +as it will disable case sensitivity checks, allowing JSP source code
  +disclosure, among other security problems./b/p
 /attribute
   
 attribute name=cacheMaxSize required=false
  @@ -118,9 +122,20 @@
   
 attribute name=caseSensitive required=false
   pIf the value of this flag is codetrue/code, all case sensitivity
  -checks will be disabled. This should not be disabled on OSes which do
  -not have a case sensitive filesystem, such as Windows. If not 
  +checks will be disabled. 

cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml engine.xml host.xml resources.xml

2003-07-30 Thread remm
remm2003/07/30 11:37:51

  Modified:webapps/docs/config context.xml engine.xml host.xml
resources.xml
  Log:
  - Document the background processing feature.
  - Document configuration of the resource cache.
  
  Revision  ChangesPath
  1.5   +22 -3 jakarta-tomcat-catalina/webapps/docs/config/context.xml
  
  Index: context.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/context.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- context.xml   15 Jan 2003 03:40:44 -  1.4
  +++ context.xml   30 Jul 2003 18:37:51 -  1.5
  @@ -47,10 +47,13 @@
   
 pIn addition to nesting strongContext/strong elements inside a
 a href=host.htmlHost/a element, you can also store them in
  -  individual files (with a .xml extension) in the codeappBase/code
  -  directory for a Host.  See
  +  individual files (with a .xml extension) in the 
  +  code$CATALINA_HOME/conf/[enginename]/[hostname]//code directory.  See
 a href=host.html#Automatic Application DeploymentAutomatic
  -  Application Deployment/a for more information./p
  +  Application Deployment/a for more information. This method allows dynamic
  +  reconfiguration of the web application, since the main 
  +  codeconf/server.xml/code file cannot be reloaded without restarting
  +  Tomcat./p
   
 pIn addition to explicitly specified Context elements, there are
 several techniques by which Context elements can be created automatically
  @@ -80,6 +83,22 @@
   support the following attributes:/p
   
   attributes
  +
  +  attribute name=backgroundProcessorDelay required=false
  +pThis value represents the delay in seconds between the 
  +invocation of the backgroundProcess method on this context and 
  +its child containers, including all wrappers. 
  +Child containers will not be invoked if their delay value is not 
  +negative (which would mean they are using their own processing 
  +thread). Setting this to a positive value will cause 
  +a thread to be spawn. After waiting the specified amount of time, 
  +the thread will invoke the backgroundProcess method on this host 
  +and all its child containers. A context will use background 
  +processing to perform session expiration and class monitoring for
  +reloading. If not specified, the default value for this attribute is 
  +-1, which means the context will rely on the background processing 
  +thread of its parent host./p
  +  /attribute
   
 attribute name=className required=false
   pJava class name of the implementation to use.  This class must
  
  
  
  1.4   +13 -0 jakarta-tomcat-catalina/webapps/docs/config/engine.xml
  
  Index: engine.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/engine.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- engine.xml15 Jan 2003 03:40:44 -  1.3
  +++ engine.xml30 Jul 2003 18:37:51 -  1.4
  @@ -39,6 +39,19 @@
   
   attributes
   
  +  attribute name=backgroundProcessorDelay required=false
  +pThis value represents the delay in seconds between the 
  +invocation of the backgroundProcess method on this engine and 
  +its child containers, including all hosts and contexts. 
  +Child containers will not be invoked if their delay value is not 
  +negative (which would mean they are using their own processing 
  +thread). Setting this to a positive value will cause 
  +a thread to be spawn. After waiting the specified amount of time, 
  +the thread will invoke the backgroundProcess method on this engine 
  +and all its child containers. If not specified, the default value for
  +this attribute is 10, which represent a 10 seconds delay./p
  +  /attribute
  +
 attribute name=className required=false
   pJava class name of the implementation to use.  This class must
   implement the codeorg.apache.catalina.Engine/code interface.
  
  
  
  1.5   +17 -1 jakarta-tomcat-catalina/webapps/docs/config/host.xml
  
  Index: host.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/host.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- host.xml  28 Jun 2003 18:48:59 -  1.4
  +++ host.xml  30 Jul 2003 18:37:51 -  1.5
  @@ -78,6 +78,22 @@
   Deployment/a for more information./p
 /attribute
   
  +  attribute name=backgroundProcessorDelay required=false
  +pThis value represents the delay in seconds 

cvs commit: jakarta-tomcat-catalina/webapps/docs/config context.xml defaultcontext.xml server.xml service.xml

2002-12-08 Thread glenn
glenn   2002/12/08 05:42:11

  Modified:catalina build.xml
   catalina/src/conf web.xml
   catalina/src/share/org/apache/catalina DefaultContext.java
   catalina/src/share/org/apache/catalina/core
StandardContext.java StandardDefaultContext.java
StandardWrapper.java
   catalina/src/share/org/apache/catalina/mbeans
mbeans-descriptors.xml
   catalina/src/share/org/apache/catalina/realm
LocalStrings.properties
   catalina/src/share/org/apache/catalina/servlets
HTMLManagerServlet.java LocalStrings.properties
ManagerServlet.java
   catalina/src/share/org/apache/catalina/session
JDBCStore.java
   webapps/ROOT/WEB-INF web.xml
   webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context
AddContextAction.java ContextForm.java
EditContextAction.java SaveContextAction.java
   webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext
AddDefaultContextAction.java
DefaultContextForm.java
EditDefaultContextAction.java
SaveDefaultContextAction.java
   webapps/docs index.xml manager-howto.xml
   webapps/docs/WEB-INF web.xml
   webapps/docs/config context.xml defaultcontext.xml
server.xml service.xml
  Added:   catalina/src/temp README.txt
  Log:
  Port bug fixes and minor changes I made to Tomcat 4 to Tomcat 5 where appropriate.
  
  Revision  ChangesPath
  1.34  +4 -0  jakarta-tomcat-catalina/catalina/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/build.xml,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- build.xml 5 Dec 2002 15:41:37 -   1.33
  +++ build.xml 8 Dec 2002 13:42:09 -   1.34
  @@ -555,6 +555,10 @@
 /fileset
   /copy
   
  +!-- JVM Temporary Directory README --
  +copy todir=${catalina.build}/temp
  +  file=src/temp/README.txt/
  +
   !-- Catalina Server Libraries --
   copy todir=${catalina.build}/server/lib
  file=${commons-beanutils.jar}/
  
  
  
  1.8   +25 -17jakarta-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.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- web.xml   16 Nov 2002 04:20:57 -  1.7
  +++ web.xml   8 Dec 2002 13:42:09 -   1.8
  @@ -89,21 +89,34 @@
 !-- following initialization parameters (default values are in square--
 !-- brackets):   --
 !--  --
  +  !--   checkInterval   If development is false and relaoding is true, --
  +  !--   background compiles are enabled. checkInterval --
  +  !--   is the time in seconds between checks to see   --
  +  !--   if a JSP page needs to be recompiled. [300]--
  +  !--  --
  +  !--   compilerWhich compiler Ant should use to compile JSP   --
  +  !--   pages.  See the Ant documenation for more  --
  +  !--   information. [javac]   --
  +  !--  --
 !--   classdebuginfo  Should the class file be compiled with --
  -  !--   debugging information?  [false]--
  +  !--   debugging information?  [true] --
 !--  --
 !--   classpath   What class path should I use while compiling   --
 !--   generated servlets?  [Created dynamically  --
 !--   based on the current web application]  --
 !--  --
  +  !--   development Is Jasper used in development mode (will check --
  +  !--   for JSP modification on every access)?  [true] --
  +  !--  --
  +  !--   enablePooling   Determines whether tag handler pooling is  --
  +  !--   enabled  [true]--
  +  !--