FIXME: This needs updates

The Context element represents a web application, which is run within a particular virtual host. Each web application is based on a Web Application Archive @@ -203,6 +205,22 @@ disclosure, among other security problems.

+ +

If true, the Tomcat classloader will take extra measures to avoid + JAR file locking when resources are accessed inside JARs through URLs. + This will impact startup time of applications, but could prove to be useful + on platforms or configurations where file locking can occur. + If not specified, the default value is false.

+ + + +

If true, Tomcat will prevent any file locking. + This will significantly impact startup time of applications, + but allows full webapp hot deploy and undeploy on platforms + or configurations where file locking can occur. + If not specified, the default value is false.

+ +

Maximum size of the static resource cache in kilobytes. If not specified, the default value is 10240 @@ -253,6 +271,12 @@ of the flag is false.

+ +

If true, Tomcat will unpack all compressed web applications before + running them. + If not specified, the default value is true.

+ +

Set to true (the default) to have Catalina enable a JNDI InitialContext for this web application that is @@ -289,11 +313,6 @@ Configure the web application class loader that will be used to load servlet and bean classes for this web application. Normally, the default configuration of the class loader will be sufficient. -

Logger - - Configure a logger that will receive - and process all log messages for this Context. This - includes application messages logged via calls to - ServletContext.log().

Manager - Configure the session manager that will be used to create, destroy, and persist HTTP sessions for this web application. Normally, the @@ -316,6 +335,13 @@

+ + +

FIXME: This needs updates

+ + + +

When you run a web server, one of the output files normally generated @@ -353,6 +379,7 @@ the following configuration steps occur automtically when Catalina is started, or whenever this web application is reloaded. No special configuration is required to enable this feature.

If you have not declared your own Loader element, a standard web application class loader will be configured. @@ -570,10 +597,9 @@ to be returned for JNDI lookups of <resource-ref> and <resource-env-ref> elements in the web application deployment descriptor. You MUST also define - Resource Parameters - for the same resource name, to configure - the object factory to be used (if not known to Tomcat already), and - the properties used to configure that object factory.
+ the needed resource parameters as attributes of the Resource + element, to configure the object factory to be used (if not known to Tomcat + already), and the properties used to configure that object factory.

For example, you can create a resource definition like this:
@@ -643,80 +669,6 @@ - - - -
This element is used to configure the resource manager (or object - factory) used to return objects when the web application performs a - JNDI lookup operation on the corresponding resource name. You - MUST define resource parameters for every resource name - that is specified by a <Resource> element inside a - <Context> or <DefaultContext> - element in $CATALINA_HOME/conf/server.xml, and/or for every - name declared in a <resource-ref> or - <resource-env-ref> element in the web application - deployment descriptor, before that resource can be successfully - accessed.
- -
Resource parameters are defined by name, and the precise set of - parameter names supported depend on the resource manager (or object - factory) you are using - they must match the names of settable JavaBeans - properties on the corresponding factory class. The JNDI implementation - will configure an instance of the specified factory class specified by - calling all the corresponding JavaBeans property setters, and then - making the factory instance available via the JNDI lookup() - call.
- -
The resource parameters for a JDBC data source might look something - like this:
- -<Context ...> - ... - <ResourceParams name="jdbc/EmployeeDB"> - <parameter> - <name>driverClassName</name> - <value>org.hsql.jdbcDriver</value> - </parameter> - <parameter> - <name>url</name> - </value>jdbc:HypersonicSQL:database</value> - </parameter> - <parameter> - <name>user</name> - <value>dbusername</value> - </parameter> - <parameter> - <name>password</name> - <value>dbpassword</value> - </parameter> - </ResourceParams> - ... -</Context> - - -
If you need to specify the Java class name of a factory class for a - particular resource type, use a <parameter> entry - named factory nested inside the - <ResourceParams> element.
- -
The valid attributes of a <ResourceParams> element - are as follows:
- - - - -
The name of the resource being configured, relative to the - java:comp/env contxt. This name MUST - match the name of a resource defined by a <Resource> - element in $CATALINA_HOME/conf/server.xml, and/or - referenced in a <resource-ref> or - <resource-env-ref> element in the web application - deployment descriptor.
- - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org