logging.properties and Filter problem

2006-10-24 Thread Ronny Batty
Hi there, I've created a logging.properties file in the WEB-INF/classes directory of one of my web contexts. This file sets the logging level to SEVERE and defines a Filter class which exists within a .jar file in the same web context. The Filter is initialized and works as expected when using

RE: logging.properties and Filter problem

2006-10-24 Thread Ronny Batty
:[EMAIL PROTECTED] Sent: 24 October 2006 16:49 To: Tomcat Users List Subject: RE: logging.properties and Filter problem From: Ronny Batty [mailto:[EMAIL PROTECTED] Subject: logging.properties and Filter problem The Filter is initialized and works as expected when using Tomcat 5.5.17

RE: logging.properties and Filter problem

2006-10-24 Thread Ronny Batty
properly. Once again thanks for the assistance. Ronny. -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: 24 October 2006 17:20 To: Tomcat Users List Subject: RE: logging.properties and Filter problem From: Ronny Batty [mailto:[EMAIL PROTECTED] Subject: RE

Wildcard role-name in auth-constraint.

2006-05-18 Thread Ronny Batty
I am using the containers JDBCRealm but would like to allow any authenticated users (without roles) to access protected resources. I realise that the handling of role-name*/role-name was modified to comply with the Servlet specification in Tomcat 5.5.x but is it really necessary to give all users