Hi, As part of Java Servlet 2.3 specs, it is possible to use the filtering feature in web applications. While I've been able to use this technique under Tomcat 4.1.30, I'm not able to be successful under JBoss 3.2.5. Based on filtering examples provided within the Tomcat release (...\webapps\examples\WEB-INF\classes\filters) or the one from Sing Li (http://www-106.ibm.com/developerworks/java/library/j-tomcat), I've deployed my sample classes and defined the necessary filter tags in the web.xml file. Starting my server is ok (in case of mistake, e.g. bad tag declaration, servlet class not in CLASSPATH, this would be mentionned in the log). Any request sent to the server works like if filtering is not taken in account.
So, my question is: Is there any configuration operation to do under JBoss in order to filtering take effect? Does some logging setting, for example the presence of log4j, would take precedence on filtering and then might disable this feature? Thanks for help View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841402#3841402 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841402 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
