Hi, It is a part of the Tomcat's user guide (http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/uguide/tomcat_ug.html). Maybe, the point 3 applies to the problem. Each Context represents a path in the Tomcat hierarchy where you place a web application. A Tomcat Context has the following configuration: 1. The path where the context is located. This can be a full path or relative to the ContextManager's home. 2. Debug level used for logging debug messages. 3. A reloadable flag. When developing a servlet it is very convenient to have Tomcat reload it upon change, this lets you fix bugs and have Tomcat test the new code without the need to shutdown and restart. To turn on servlet reloading set the reloadable flag to true. Detecting changes however is time consuming; moreover, since the new servlets are getting loaded in a new class-loader object there are cases where this class-reloading trigger casts errors. To avoid these problems you can set the reloadable flag to false; this will disable the autoreload feature. Mit freundlichen Grüßen Christian Schildt Diplom-Betriebswirt (FH) Softwaredeveloper Phone: 089/89013023 Mailto: [EMAIL PROTECTED] ________________________________________________ ELAXY AG Gutenbergstr. 5 D-82178 Puchheim bei München Phone: +089/8901300 Fax: +089/89013089 www.elaxy.com ________________________________________________ "Francesco Marsoni" An: <[EMAIL PROTECTED]> <[EMAIL PROTECTED] Kopie: enze.it> Thema: Tomcat 4 - Filter problem 02.05.2001 13:40 Bitte antworten an tomcat-user I wrote a filter. Put it in a jar file and added to classpath. This is the result: java.lang.ClassCastException: net.indaco.klyx.auth.tomcat.KlyxFilter at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilter Config.java:250) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFil terConfig.java:311) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterCon fig.java:120) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:28 81) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3118) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1059) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1059) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:253) at org.apache.catalina.core.StandardService.start(StandardService.java:353) at org.apache.catalina.core.StandardServer.start(StandardServer.java:458) at org.apache.catalina.startup.Catalina.start(Catalina.java:707) at org.apache.catalina.startup.Catalina.execute(Catalina.java:627) at org.apache.catalina.startup.Catalina.process(Catalina.java:177) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:177) If I put the filter class in WEB-INF/classes all goes well. Where's the problem? I got a similar exception writing a custom Realm to authenticate against. Thx Francesco
