jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15488] - BeanInfoManager uses double-checked locking
Date Wed, 18 Dec 2002 16:42:54 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=15488>.
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:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>


Mime
View raw message