Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 48993 invoked from network); 10 Nov 2002 09:38:01 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Nov 2002 09:38:01 -0000 Received: (qmail 347 invoked by uid 97); 10 Nov 2002 09:39:08 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 327 invoked by uid 97); 10 Nov 2002 09:39:08 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 316 invoked by uid 50); 10 Nov 2002 09:39:07 -0000 Date: 10 Nov 2002 09:39:07 -0000 Message-ID: <20021110093907.315.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 14394] - Excessive exceptions log under security manager X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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: For additional commands, e-mail: