You might get a lot more help if you would send you web.xml file as well. Here is mine
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN " "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"> <web-app> <context-param> <param-name>XyloWeb</param-name> <param-value>[EMAIL PROTECTED]</param-value> <description> XSLT Rendering Servlet </description> </context-param> <servlet> <servlet-name>XyloServlet</servlet-name> <description> XSLT Rendering Servlet </description> <servlet-class>XyloServlet</servlet-class> </servlet> <servlet> <servlet-name>Status</servlet-name> <description> Servlet for testing purposes </description> <servlet-class>Status</servlet-class> </servlet> <servlet> <servlet-name>CreateBulletinMessage</servlet-name> <description> Add message to bulletin </description> <servlet-class>CreateBulletinMessage</servlet-class> </servlet> <servlet> <servlet-name>ListBulletinMessages</servlet-name> <description> Lists all messages on the board </description> <servlet-class>ListBulletinMessages</servlet-class> </servlet> <servlet-mapping> <servlet-name>XyloServlet</servlet-name> <url-pattern>/xyloservlet</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Status</servlet-name> <url-pattern>/status</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>CreateBulletinMessage</servlet-name> <url-pattern>/createbulletinmessage</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>ListBulletinMessages</servlet-name> <url-pattern>/listbulletinmessages</url-pattern> </servlet-mapping> <session-config> <session-timeout> 30 </session-timeout> </servlet-mapping> <servlet-mapping> <servlet-name>CreateBulletinMessage</servlet-name> <url-pattern>/createbulletinmessage</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>ListBulletinMessages</servlet-name> <url-pattern>/listbulletinmessages</url-pattern> </servlet-mapping> <session-config> <session-timeout> 30 </session-timeout> </session-config> <welcome-file-list> <welcome-file> index.html </welcome-file> </welcome-file-list> </web-app> my class file (Status.class is stored in Web-inf/classes) Have fun Alex On Saturday, June 8, 2002, at 09:22 PM, puneet sachar wrote: > Hi friends, this is my 4th mail regarding my single > complain.. > > I have install the tomcat 4.0.3 and its doing fine as > far .html files are concern but no .class and .jsp > files are running on it > > I have asked 9-10 times abt same question again and > again and I got nothing from u guys there > > Plz help meÖI really stuck .. > > With this mail Iím sending my server.xml file and > web.xml file which is in my virtualhost/WEB-INF/ > > I know it is very tough for u to go in these files and > see for errors but plz..iím in need badly and afater > spending so much time here I some time feel like > crying Ö and Iím in such a place and in such a part of > India..where I canít get ant local computer guy with > whom I can discuss ..plz do me a little favour > > Here are my problems > 1) no .class and .jsp working only html is working > 2) I have done all changes which were to made in > server.xmlÖ)I have send the file also plz check it and > tell me any mistake if u find) > 3) Iím getting 404 error ..no servlet found > 4) And Iím able to excess the .class file vis > http://localhost:80/examples/servlet/abc.class > But not by making my own virtual host aand not even > the default root directory > > > what i have is my own context named sachar > and when i go > .http://puneet:80/sachar/servlet/HelloworldServlet > > error -- 404 > > See friends ..if u can help me Iíll be very grateful > to u > > Puneet > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > <?xml version="1.0" encoding="ISO-8859-1"?> > > <!DOCTYPE web-app > PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" > "http://java.sun.com/dtd/web-app_2_3.dtd"> > > <web-app> > <servlet> > <servlet-name>MyExample</servlet-name> > <servlet-class>HelloWorldExample</servlet-class> > <run-as> > <description>Security role for anonymous access</description> > <role-name>tomcat</role-name> > </run-as> > </servlet> > > <servlet-mapping> > <servlet-name>MyExample</servlet-name> > <url-pattern>/sachar/servlet/snoop</url-pattern> > <url-pattern>/servlet/*</url-pattern> > </servlet-mapping> > > > </web-app> > <!-- Example Server Configuration File --> > <!-- Note that component elements are nested corresponding to their > parent-child relationships with each other --> > > <!-- A "Server" is a singleton element that represents the entire JVM, > which may contain one or more "Service" instances. The Server > listens for a shutdown command on the indicated port. > > Note: A "Server" is not itself a "Container", so you may not > define subcomponents such as "Valves" or "Loggers" at this level. > --> > > <Server port="8005" shutdown="SHUTDOWN" debug="0"> > > > <!-- A "Service" is a collection of one or more "Connectors" that > share > a single "Container" (and therefore the web applications visible > within that Container). Normally, that Container is an "Engine", > but this is not required. > > Note: A "Service" is not itself a "Container", so you may not > define subcomponents such as "Valves" or "Loggers" at this level. > --> > > <!-- Define the Tomcat Stand-Alone Service --> > <Service name="Tomcat-Standalone"> > > <!-- A "Connector" represents an endpoint by which requests are > received > and responses are returned. Each Connector passes requests on > to the > associated "Container" (normally an Engine) for processing. > > By default, a non-SSL HTTP/1.1 Connector is established on > port 8080. > You can also enable an SSL HTTP/1.1 Connector on port 8443 by > following the instructions below and uncommenting the second > Connector > entry. SSL support requires the following steps (see the SSL > Config > HOWTO in the Tomcat 4.0 documentation bundle for more detailed > instructions): > * Download and install JSSE 1.0.2 or later, and put the JAR > files > into "$JAVA_HOME/jre/lib/ext". > * Execute: > %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA > (Windows) > $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA > (Unix) > with a password value of "changeit" for both the certificate > and > the keystore itself. > > By default, DNS lookups are enabled when a web application > calls > request.getRemoteHost(). This can have an adverse impact on > performance, so you can disable it by setting the > "enableLookups" attribute to "false". When DNS lookups are > disabled, > request.getRemoteHost() will return the String version of the > IP address of the remote client. > --> > > <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> > <Connector > className="org.apache.catalina.connector.http.HttpConnector" > port="80" minProcessors="5" maxProcessors="75" > enableLookups="true" redirectPort="8443" > acceptCount="10" debug="0" connectionTimeout="60000"/> > <!-- Note : To disable connection timeouts, set connectionTimeout > value > to -1 --> > > <!-- Define an SSL HTTP/1.1 Connector on port 8443 --> > <!-- > <Connector > className="org.apache.catalina.connector.http.HttpConnector" > port="8443" minProcessors="5" maxProcessors="75" > enableLookups="true" > acceptCount="10" debug="0" scheme="https" secure="true"> > <Factory > className="org.apache.catalina.net.SSLServerSocketFactory" > clientAuth="false" protocol="TLS"/> > </Connector> > --> > > <!-- Define an AJP 1.3 Connector on port 8009 --> > <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" > port="8009" minProcessors="5" maxProcessors="75" > acceptCount="10" debug="0"/> > > <!-- Define a Proxied HTTP/1.1 Connector on port 8081 --> > <!-- See proxy documentation for more information about using > this. --> > <!-- > <Connector > className="org.apache.catalina.connector.http.HttpConnector" > port="8081" minProcessors="5" maxProcessors="75" > enableLookups="true" > acceptCount="10" debug="0" connectionTimeout="60000" > proxyPort="80"/> > --> > > <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 --> > <!-- > <Connector > className="org.apache.catalina.connector.http10.HttpConnector" > port="8082" minProcessors="5" maxProcessors="75" > enableLookups="true" redirectPort="8443" > acceptCount="10" debug="0"/> > --> > > <!-- An Engine represents the entry point (within Catalina) that > processes > every request. The Engine implementation for Tomcat stand > alone > analyzes the HTTP headers included with the request, and > passes them > on to the appropriate Host (virtual host). --> > > <!-- Define the top level container in our container hierarchy --> > > > > > <Engine name="Standalone" defaultHost="localhost" debug="0"> > > <!-- The request dumper valve dumps useful debugging information > about > the request headers and cookies that were received, and the > response > headers and cookies that were sent, for all requests > received by > this instance of Tomcat. If you care only about requests > to a > particular virtual host, or a particular application, nest > this > element inside the corresponding <Host> or <Context> entry > instead. > > For a similar mechanism that is portable to all Servlet 2.3 > containers, check out the "RequestDumperFilter" Filter in the > example application (the source for this filter may be found > in > "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters"). > > Request dumping is disabled by default. Uncomment the > following > element to enable it. --> > <!-- > <Valve className="org.apache.catalina.valves.RequestDumperValve"/> > --> > > <!-- Global logger unless overridden at lower levels --> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="catalina_log." suffix=".txt" > timestamp="true"/> > > <!-- Because this Realm is here, an instance will be shared > globally --> > > <Realm className="org.apache.catalina.realm.MemoryRealm" /> > > <!-- Replace the above Realm with one of the following to get a > Realm > stored in a database and accessed via JDBC --> > > <!-- > <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" > driverName="org.gjt.mm.mysql.Driver" > > connectionURL="jdbc:mysql://localhost/authority?user=test;password=test" > userTable="users" userNameCol="user_name" > userCredCol="user_pass" > userRoleTable="user_roles" roleNameCol="role_name" /> > --> > > <!-- > <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" > driverName="oracle.jdbc.driver.OracleDriver" > > connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL?user=scott;password=tiger" > userTable="users" userNameCol="user_name" > userCredCol="user_pass" > userRoleTable="user_roles" roleNameCol="role_name" /> > --> > > <!-- > <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" > driverName="sun.jdbc.odbc.JdbcOdbcDriver" > connectionURL="jdbc:odbc:CATALINA" > userTable="users" userNameCol="user_name" > userCredCol="user_pass" > userRoleTable="user_roles" roleNameCol="role_name" /> > --> > > <!-- Define the default virtual host --> > <Host name="localhost" debug="0" appBase="webapps" > unpackWARs="true"> > > <!-- Normally, users must authenticate themselves to each web > app > individually. Uncomment the following entry if you would > like > a user to be authenticated the first time they encounter a > resource protected by a security constraint, and then have > that > user identity maintained across *all* web applications > contained > in this virtual host. --> > <!-- > <Valve > className="org.apache.catalina.authenticator.SingleSignOn" > debug="0"/> > --> > > <!-- Access log processes all requests for this virtual host. > By > default, log files are created in the "logs" directory > relative to > $CATALINA_HOME. If you wish, you can specify a different > directory with the "directory" attribute. Specify either > a relative > (to $CATALINA_HOME) or absolute path to the desired > directory. > --> > <Valve className="org.apache.catalina.valves.AccessLogValve" > directory="logs" prefix="localhost_access_log." > suffix=".txt" > pattern="common"/> > > > <!-- Logger shared by all Contexts related to this virtual > host. By > default (when using FileLogger), log files are created in > the "logs" > directory relative to $CATALINA_HOME. If you wish, you > can specify > a different directory with the "directory" attribute. > Specify either a > relative (to $CATALINA_HOME) or absolute path to the > desired > directory.--> > <Logger className="org.apache.catalina.logger.FileLogger" > directory="logs" prefix="localhost_log." suffix=".txt" > timestamp="true"/> > > > <!-- Define properties for each web application. This is only > needed > if you want to set non-default properties, or have web > application > document roots in places other than the virtual host's > appBase > directory. --> > > <!-- Tomcat Root Context --> > <!-- > <Context path="" docBase="ROOT" debug="0"/> > --> > > <!-- Tomcat Manager Context --> > <Context path="/manager" docBase="manager" > debug="0" privileged="true"/> > > <!-- Tomcat Examples Context --> > <Context path="/examples" docBase="examples" debug="0" > reloadable="true" crossContext="true"> > > > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="localhost_examples_log." suffix=".txt" > timestamp="true"/> > > > <Ejb name="ejb/EmplRecord" type="Entity" > home="com.wombat.empl.EmployeeRecordHome" > remote="com.wombat.empl.EmployeeRecord"/> > <!-- PersistentManager: Uncomment the section below to test > Persistent > Sessions. > > saveOnRestart: If true, all active sessions will be saved > to the Store when Catalina is shutdown, regardless of > other settings. All Sessions found in the Store will be > loaded on startup. Sessions past their expiration are > ignored in both cases. > maxActiveSessions: If 0 or greater, having too many > active > sessions will result in some being swapped out. > minIdleSwap > limits this. -1 means unlimited sessions are allowed. > 0 means sessions will almost always be swapped out > after > use - this will be noticeably slow for your users. > minIdleSwap: Sessions must be idle for at least this long > (in seconds) before they will be swapped out due to > maxActiveSessions. This avoids thrashing when the site is > highly active. -1 or 0 means there is no minimum - > sessions > can be swapped out at any time. > maxIdleSwap: Sessions will be swapped out if idle for > this > long (in seconds). If minIdleSwap is higher, then it > will > override this. This isn't exact: it is checked > periodically. > -1 means sessions won't be swapped out for this reason, > although they may be swapped out for maxActiveSessions. > If set to >= 0, guarantees that all sessions found in > the > Store will be loaded on startup. > maxIdleBackup: Sessions will be backed up (saved to the > Store, > but left in active memory) if idle for this long (in > seconds), > and all sessions found in the Store will be loaded on > startup. > If set to -1 sessions will not be backed up, 0 means > they > should be backed up shortly after being used. > > To clear sessions from the Store, set maxActiveSessions, > maxIdleSwap, > and minIdleBackup all to -1, saveOnRestart to false, > then restart > Catalina. > --> > <!-- > <Manager > className="org.apache.catalina.session.PersistentManager" > debug="0" > saveOnRestart="true" > maxActiveSessions="-1" > minIdleSwap="-1" > maxIdleSwap="-1" > maxIdleBackup="-1"> > <Store > className="org.apache.catalina.session.FileStore"/> > </Manager> > --> > <Environment name="maxExemptions" type="java.lang.Integer" > value="15"/> > <Parameter name="context.param.name" > value="context.param.value" > override="false"/> > <Resource name="jdbc/EmployeeAppDb" auth="SERVLET" > type="javax.sql.DataSource"/> > <ResourceParams name="jdbc/EmployeeAppDb"> > <parameter><name>user</name><value>sa</value></parameter> > <parameter><name>password</name><value></value></parameter> > <parameter><name>driverClassName</name> > <value>org.hsql.jdbcDriver</value></parameter> > <parameter><name>driverName</name> > <value>jdbc:HypersonicSQL:database</value></parameter> > </ResourceParams> > <Resource name="mail/Session" auth="Container" > type="javax.mail.Session"/> > <ResourceParams name="mail/Session"> > <parameter> > <name>mail.smtp.host</name> > <value>localhost</value> > </parameter> > </ResourceParams> > </Context> > > </Host> > > </Engine> > > <!-- NEW ENTRY GOES HERE --> > > > <Engine name="Standalone" defaultHost="puneet" debug="0"> > > <!-- The request dumper valve dumps useful debugging information > about > the request headers and cookies that were received, and the > response > headers and cookies that were sent, for all requests > received by > this instance of Tomcat. If you care only about requests > to a > particular virtual host, or a particular application, nest > this > element inside the corresponding <Host> or <Context> entry > instead. > > For a similar mechanism that is portable to all Servlet 2.3 > containers, check out the "RequestDumperFilter" Filter in the > example application (the source for this filter may be found > in > "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters"). > > Request dumping is disabled by default. Uncomment the > following > element to enable it. --> > <!-- > <Valve className="org.apache.catalina.valves.RequestDumperValve"/> > --> > > <!-- Global logger unless overridden at lower levels --> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="catalina_log." suffix=".txt" > timestamp="true"/> > > <!-- Because this Realm is here, an instance will be shared > globally --> > > <Realm className="org.apache.catalina.realm.MemoryRealm" /> > > <!-- Replace the above Realm with one of the following to get a > Realm > stored in a database and accessed via JDBC --> > > <!-- > <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" > driverName="org.gjt.mm.mysql.Driver" > > connectionURL="jdbc:mysql://localhost/authority?user=test;password=test" > userTable="users" userNameCol="user_name" > userCredCol="user_pass" > userRoleTable="user_roles" roleNameCol="role_name" /> > --> > > <!-- > <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" > driverName="oracle.jdbc.driver.OracleDriver" > > connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL?user=scott;password=tiger" > userTable="users" userNameCol="user_name" > userCredCol="user_pass" > userRoleTable="user_roles" roleNameCol="role_name" /> > --> > > <!-- > <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" > driverName="sun.jdbc.odbc.JdbcOdbcDriver" > connectionURL="jdbc:odbc:CATALINA" > userTable="users" userNameCol="user_name" > userCredCol="user_pass" > userRoleTable="user_roles" roleNameCol="role_name" /> > --> > > <!-- Define the default virtual host --> > > <Host name="puneet" debug="0" appBase="webapps" unpackWARs="true"> > > <!-- Normally, users must authenticate themselves to each web > app > individually. Uncomment the following entry if you would > like > a user to be authenticated the first time they encounter a > resource protected by a security constraint, and then have > that > user identity maintained across *all* web applications > contained > in this virtual host. --> > <!-- > <Valve > className="org.apache.catalina.authenticator.SingleSignOn" > debug="0"/> > --> > > <!-- Access log processes all requests for this virtual host. > By > default, log files are created in the "logs" directory > relative to > $CATALINA_HOME. If you wish, you can specify a different > directory with the "directory" attribute. Specify either > a relative > (to $CATALINA_HOME) or absolute path to the desired > directory. > --> > <Valve className="org.apache.catalina.valves.AccessLogValve" > directory="logs" prefix="puneet_access_log." > suffix=".txt" > pattern="common"/> > > > <!-- Logger shared by all Contexts related to this virtual > host. By > default (when using FileLogger), log files are created in > the "logs" > directory relative to $CATALINA_HOME. If you wish, you > can specify > a different directory with the "directory" attribute. > Specify either a > relative (to $CATALINA_HOME) or absolute path to the > desired > directory.--> > <Logger className="org.apache.catalina.logger.FileLogger" > directory="logs" prefix="puneet_log." suffix=".txt" > timestamp="true"/> > > > <!-- Define properties for each web application. This is only > needed > if you want to set non-default properties, or have web > application > document roots in places other than the virtual host's > appBase > directory. --> > > <!-- Tomcat Root Context --> > <!-- > <Context path="" docBase="ROOT" debug="0"/> > --> > > <!-- Tomcat Own Context --> > > > <Context path="/sachar" docBase="sachar" debug="0" > reloadable="true" crossContext="true"> > > > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="puneet_examples_log." suffix=".txt" > timestamp="true"/> > > > <Ejb name="ejb/EmplRecord" type="Entity" > home="com.wombat.empl.EmployeeRecordHome" > remote="com.wombat.empl.EmployeeRecord"/> > <!-- PersistentManager: Uncomment the section below to test > Persistent > Sessions. > > saveOnRestart: If true, all active sessions will be saved > to the Store when Catalina is shutdown, regardless of > other settings. All Sessions found in the Store will be > loaded on startup. Sessions past their expiration are > ignored in both cases. > maxActiveSessions: If 0 or greater, having too many > active > sessions will result in some being swapped out. > minIdleSwap > limits this. -1 means unlimited sessions are allowed. > 0 means sessions will almost always be swapped out > after > use - this will be noticeably slow for your users. > minIdleSwap: Sessions must be idle for at least this long > (in seconds) before they will be swapped out due to > maxActiveSessions. This avoids thrashing when the site is > highly active. -1 or 0 means there is no minimum - > sessions > can be swapped out at any time. > maxIdleSwap: Sessions will be swapped out if idle for > this > long (in seconds). If minIdleSwap is higher, then it > will > override this. This isn't exact: it is checked > periodically. > -1 means sessions won't be swapped out for this reason, > although they may be swapped out for maxActiveSessions. > If set to >= 0, guarantees that all sessions found in > the > Store will be loaded on startup. > maxIdleBackup: Sessions will be backed up (saved to the > Store, > but left in active memory) if idle for this long (in > seconds), > and all sessions found in the Store will be loaded on > startup. > If set to -1 sessions will not be backed up, 0 means > they > should be backed up shortly after being used. > > To clear sessions from the Store, set maxActiveSessions, > maxIdleSwap, > and minIdleBackup all to -1, saveOnRestart to false, > then restart > Catalina. > --> > <!-- > <Manager > className="org.apache.catalina.session.PersistentManager" > debug="0" > saveOnRestart="true" > maxActiveSessions="-1" > minIdleSwap="-1" > maxIdleSwap="-1" > maxIdleBackup="-1"> > <Store > className="org.apache.catalina.session.FileStore"/> > </Manager> > --> > <Environment name="maxExemptions" type="java.lang.Integer" > value="15"/> > <Parameter name="context.param.name" > value="context.param.value" > override="false"/> > <Resource name="jdbc/EmployeeAppDb" auth="SERVLET" > type="javax.sql.DataSource"/> > <ResourceParams name="jdbc/EmployeeAppDb"> > <parameter><name>user</name><value>sa</value></parameter> > <parameter><name>password</name><value></value></parameter> > <parameter><name>driverClassName</name> > <value>org.hsql.jdbcDriver</value></parameter> > <parameter><name>driverName</name> > <value>jdbc:HypersonicSQL:database</value></parameter> > </ResourceParams> > <Resource name="mail/Session" auth="Container" > type="javax.mail.Session"/> > <ResourceParams name="mail/Session"> > <parameter> > <name>mail.smtp.host</name> > <value>localhost</value> > </parameter> > </ResourceParams> > </Context> > > </Host> > > </Engine> > > > > <!-- NEW ENTY GOES ABOVE --> > > > > </Service> > > <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with > Tomcat 4.0 > as its servlet container. Please read the README.txt file coming > with > the WebApp Module distribution on how to build it. > (Or check out the "jakarta-tomcat-connectors/webapp" CVS > repository) > > To configure the Apache side, you must ensure that you have the > "ServerName" and "Port" directives defined in "httpd.conf". > Then, > lines like these to the bottom of your "httpd.conf" file: > > LoadModule webapp_module libexec/mod_webapp.so > WebAppConnection warpConnection warp localhost:8008 > WebAppDeploy examples warpConnection /examples/ > > The next time you restart Apache (after restarting Tomcat, if > needed) > the connection will be established, and all applications you make > visible via "WebAppDeploy" directives can be accessed through > Apache. > --> > > <!-- Define an Apache-Connector Service --> > <Service name="Tomcat-Apache"> > > <Connector > className="org.apache.catalina.connector.warp.WarpConnector" > port="8008" minProcessors="5" maxProcessors="75" > enableLookups="true" appBase="webapps" > acceptCount="10" debug="0"/> > > <!-- Replace "localhost" with what your Apache "ServerName" is set > to --> > <Engine className="org.apache.catalina.connector.warp.WarpEngine" > name="Apache" debug="0"> > > <!-- Global logger unless overridden at lower levels --> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="apache_log." suffix=".txt" > timestamp="true"/> > > <!-- Because this Realm is here, an instance will be shared > globally --> > <Realm className="org.apache.catalina.realm.MemoryRealm" /> > > </Engine> > > </Service> > > </Server> > > -- > To unsubscribe, e-mail: <mailto:tomcat-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:tomcat-user- > [EMAIL PROTECTED]>