tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12707] - Problems with Component class name in JSP
Date Tue, 24 Sep 2002 00:57:09 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=12707>.
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=12707

Problems with Component class name in JSP

jan.luehe@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From jan.luehe@sun.com  2002-09-24 00:57 -------
This is a known problem that is scheduled to be fixed in J2SE 1.4.2.

This problem occurs only when introspecting a bean named "Component".

By default, the Introspector adds "sun.beans.infos" to the search path
for explicit BeanInfos. "sun.beans.infos" contains a single class:
"ComponentBeanInfo".

When introspecting a class, the Introspector checks to see if an
explicit BeanInfo for the class exists in the search path. If the
class being introspected is named "Component", the Introspector finds
a match: "sun.beans.infos.ComponentBeanInfo" in its search path and
uses it, even though "sun.beans.infos.ComponentBeanInfo" really is
intended as the BeanInfo for "java.awt.Component".

The existing bug reports on this problem mention 2 workarounds: 

- Set the BeanInfo search path to an empty array, as in:

    Introspector.setBeanInfoSearchPath(new String[] { });

  This workaround would have to be implemented by Jasper.

- Tag library authors may implement their own explicit "ComponentBeanInfo"
  class and place it in the same package as their "Component" class.

Since this is a known problem in the underlying Java runtime that is
going to be fixed in the upcoming J2SE 1.4.2 release, and for which a
workaround exists that may be implemented by tag library authors, we
are not going to implement the workaround in Jasper.

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


Mime
View raw message