Return-Path: Delivered-To: apmail-jakarta-taglibs-dev-archive@apache.org Received: (qmail 42602 invoked from network); 18 Dec 2002 16:41:44 -0000 Received: from exchange.sun.com (HELO nagoya.betaversion.org) (192.18.33.10) by daedalus.apache.org with SMTP; 18 Dec 2002 16:41:44 -0000 Received: (qmail 14044 invoked by uid 97); 18 Dec 2002 16:42:55 -0000 Delivered-To: qmlist-jakarta-archive-taglibs-dev@jakarta.apache.org Received: (qmail 14025 invoked by uid 97); 18 Dec 2002 16:42:54 -0000 Mailing-List: contact taglibs-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tag Libraries Developers List" Reply-To: "Tag Libraries Developers List" Delivered-To: mailing list taglibs-dev@jakarta.apache.org Received: (qmail 14014 invoked by uid 50); 18 Dec 2002 16:42:54 -0000 Date: 18 Dec 2002 16:42:54 -0000 Message-ID: <20021218164254.14013.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: taglibs-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 15488] - BeanInfoManager uses double-checked locking 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=15488 BeanInfoManager uses double-checked locking ------- Additional Comments From schultz@adrenaline.com 2002-12-18 16:42 ------- Sorry. Yes, I'm talking about the EL implementation. org.apache.taglibs.standard.lang.jstl.BeanInfoManager An unrelated question about the BeanManager: A colleague of mine was using a class called Component and it blew up when used within the EL because the Introspector was finding a BeanInfo for java.awt.Component and no BeanInfo for his Component class. It took forever to figure it out. It looks like possible solutions are: 1. Write a BeanInfo class for his class, as well as for all other classes he uses with the JSTL 2. Set the 'bean info path' to nothing to force the use of reflection 3. Hack the BeanInfoManager to use IGNORE_ALL_BEANINFO when incoking the Introspector. None of these seem like great ideas. Got any of your own? >:| -- To unsubscribe, e-mail: For additional commands, e-mail: