You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/08/19 04:18:46 UTC
DO NOT REPLY [Bug 30743] New: -
Custom attributes handled differently in 5.0.27.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30743>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30743
Custom <Realm> attributes handled differently in 5.0.27.
Summary: Custom <Realm> attributes handled differently in 5.0.27.
Product: Tomcat 5
Version: 5.0.27
Platform: All
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: sjdavies@acm.org
To implement a custom login attempt counter I extended the DataSourceRealm
class in 5.0.19 & 5.0.25. Several extra attributes were added to the standard
<Realm> element in the applications context.xml eg.
<Realm
className="mypkg.MyDataSourceRealm"
dataSourceName="jdbc/ebira"
debug="99"
localDataSource="true"
maxLoginAttempts="3"
roleNameCol="role"
userCredCol="pwd"
userInvalidCountCol="invalidCount"
userNameCol="userid"
userRoleTable="userRole"
userTable="person"/>
My custom realm class subclassed DataSourceRealm & had fields to store the
additional attributes. This worked fine in 5.0.19 & 5.0.25.
For some reason a change has been made in 5.0.27 that prevents the setter
methods for the additional attributes from being invoked. eg. setUserTable is
still invoked but setMaxLoginAttempts is not.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org