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=29048>. 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=29048 Request changes to java permissions in DataSourceRealm ------- Additional Comments From [EMAIL PROTECTED] 2004-05-18 10:57 ------- As you say, providing a view will provide some of the required function without code modification. The problem is that if the users fails authentication the counter must be increased, if the users passes authentication the counter is zeroed. That may be possible in a view but I can't see how to do it. This is not a request for user-specific code to be placed in DSR. It is simply an enhancement request to change method visibility from private to protected. This will not 'bloat' the code space. Classes are often used in ways the original designer did not cater for. In attempting to reuse the functionality of DSR through subclassing, problems were encountered. Because methods such as open, close & credentials were private they had to be re-implemented in the subclass even though they were direct copies of the superclass implementations. The authenticate(x2 params) method had to be copied because it relied on the private authenticate(x3 params). Changing the visibility will mean that app-specific subclasses can simply override authenticate(x3). Surely this level of reuse is desirable? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
