commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14394] - Excessive exceptions log under security manager
Date Sun, 10 Nov 2002 09:39:07 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14394>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14394

Excessive exceptions log under security manager





------- Additional Comments From cmlenz@apache.org  2002-11-10 09:39 -------
While I would prefer BeanUtils to remember it's running under a SecurityManager
where setAccessible() will fail (using a static boolean flag or such), I'm not
sure whether such an approach wouldn't cause problems.

So, at the very least, I think the exception should be logged at DEBUG level
instead of at WARN. If the exception was only logged once, WARN would be ok, but
not if it is logged on every invocation as it is now.

Patch that changes the log-level has been attached.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message