changeset 1998:d72275039339

6905574: DOC: Introspector's javadoc contains wrong statement Reviewed-by: gsm
author malenkov
date Wed, 09 Dec 2009 11:38:30 +0300
parents 931cfd3ba5b6
children f012e2c094ff
files src/share/classes/java/beans/Introspector.java
diffstat 1 files changed, 0 insertions(+), 13 deletions(-) [+]
line wrap: on
line diff
--- a/src/share/classes/java/beans/Introspector.java	Wed Dec 09 11:34:18 2009 +0300
+++ b/src/share/classes/java/beans/Introspector.java	Wed Dec 09 11:38:30 2009 +0300
@@ -78,20 +78,7 @@
  * patterns to identify property accessors, event sources, or public
  * methods.  We then proceed to analyze the class's superclass and add
  * in the information from it (and possibly on up the superclass chain).
- *
  * <p>
- * Because the Introspector caches BeanInfo classes for better performance,
- * take care if you use it in an application that uses
- * multiple class loaders.
- * In general, when you destroy a <code>ClassLoader</code>
- * that has been used to introspect classes,
- * you should use the
- * {@link #flushCaches <code>Introspector.flushCaches</code>}
- * or
- * {@link #flushFromCaches <code>Introspector.flushFromCaches</code>} method
- * to flush all of the introspected classes out of the cache.
- *
- * <P>
  * For more information about introspection and design patterns, please
  * consult the
  *  <a href="http://java.sun.com/products/javabeans/docs/index.html">JavaBeans specification</a>.