-
Bug
-
Resolution: Not an Issue
-
P4
-
None
-
1.4.0
-
sparc
-
solaris_2.6
Name: dsR10051 Date: 07/10/2001
The documentation for the following methods of class java.beans.Introspector:
public static BeanInfo getBeanInfo(Class beanClass)
public static BeanInfo getBeanInfo(Class beanClass, int flags)
public static BeanInfo getBeanInfo(Class beanClass, Class stopClass)
is not complete.
Javadoc for these methods contains the assertion:
...
* If the BeanInfo class for a Java Bean has been previously Introspected
* based on the same arguments, then the BeanInfo class is retrieved
* from the BeanInfo cache.
...
This assertion should be completed to follow to the implementation
of the BeanInfo cache. Introspector uses the WeakHashMap
for the caching purposes. It allows to automatically remove
the cached information by the garbage collector (see #4291376).
This behavior should be documented because the cash flushing
is not follow from the existent documentation.
Please note, the implementation of the BeanInfo cache does not satisfy to
requirements that declared in 4291376. There are the situations
when the class is referenced by the program, but the cash is flushed
by the garbage collector.
======================================================================
The documentation for the following methods of class java.beans.Introspector:
public static BeanInfo getBeanInfo(Class beanClass)
public static BeanInfo getBeanInfo(Class beanClass, int flags)
public static BeanInfo getBeanInfo(Class beanClass, Class stopClass)
is not complete.
Javadoc for these methods contains the assertion:
...
* If the BeanInfo class for a Java Bean has been previously Introspected
* based on the same arguments, then the BeanInfo class is retrieved
* from the BeanInfo cache.
...
This assertion should be completed to follow to the implementation
of the BeanInfo cache. Introspector uses the WeakHashMap
for the caching purposes. It allows to automatically remove
the cached information by the garbage collector (see #4291376).
This behavior should be documented because the cash flushing
is not follow from the existent documentation.
Please note, the implementation of the BeanInfo cache does not satisfy to
requirements that declared in 4291376. There are the situations
when the class is referenced by the program, but the cash is flushed
by the garbage collector.
======================================================================