costin 02/01/06 00:58:31
Modified: jk/conf web.xml
Log:
Added the declaration for JkServlet. All settings for jk2 are done in web.xml
( well, not quite - probably we'll also support workers.properties so the user
changes only one place, and we may also support Interceptor/Connector style, etc ).
The use of web.xml has few big benefits:
- any servlet developer should know very well it's structure.
- any tool that is managing webapps can be used to configure jk. And to
deploy/upgrade jk, as long as it supports the 'priviledged' flag.
Also, the use of the webapp will allow us to use the predefined environment
and locations.
Revision Changes Path
1.2 +35 -8 jakarta-tomcat-connectors/jk/conf/web.xml
Index: web.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/conf/web.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- web.xml 30 Oct 2001 16:44:16 -0000 1.1
+++ web.xml 6 Jan 2002 08:58:31 -0000 1.2
@@ -5,12 +5,39 @@
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd";>
<web-app>
-<!-- This will plug the 4.0 adapter, but some issues need to be
- figured first
- <servlet>
- <servlet-name>JkServlet</servlet-name>
- <servlet-class>org.apache.ajp.tomcat4.JkServlet</servlet-class>
- <load-on-startup>1</load-on-startup>
- </servlet>
- -->
+ <servlet>
+ <servlet-name>JkServlet</servlet-name>
+ <servlet-class>org.apache.jk.server.JkServlet</servlet-class>
+ <init-param>
+ <param-name>listenAddress</param-name>
+ <param-value></param-value>
+ <description>Address to listen on. Default to WEB-INF/work/tomcatSocket
+for unix domain sockets and pipes and 8089 for TCP</description>
+ </init-param>
+
+ <init-param>
+ <param-name>channel</param-name>
+ <param-value>org.apache.jk.common.ChannelUn</param-value>
+ <description>Channel used for communication. Use
org.apache.jk.common.ChannelUn
+for unix sockets, org.apache.jk.common.ChannelSocket for TCP. XXX multi-value,
multiple
+channels ?</description>
+ </init-param>
+
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <!-- Hack - this will be loaded if 4.0 is detected. It'll not be loaded at
+ startup, and 3.3 will just ignore it. We need JkServlet to be a 'plain'
+ servlet, with no dependencies ( so it loads and log messages in any
+ condition ). It'll use Class.forName or other means to load container
+ specific classes. In particular, for 4.0 the only way for a trusted
+ app to gain access to the container is by a servlet starting with
'o.a.catalina'
+ and implementing a specific interface. The servlet seem to need to be
+ declared here, so we can play our init tricks. In future we hope for
+ a cleaner mechanism. -->
+ <servlet>
+ <servlet-name>JkServlet40</servlet-name>
+ <servlet-class>org.apache.catalina.jk.JkServlet40</servlet-class>
+ </servlet>
+
</web-app>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
