From dc08e5047988ac80b318683c69eecc5847406420 Mon Sep 17 00:00:00 2001 From: Sergey Malenkov Date: Wed, 9 Dec 2009 11:38:30 +0300 Subject: [PATCH] 6905574: DOC: Introspector's javadoc contains wrong statement Reviewed-by: gsm --- jdk/src/share/classes/java/beans/Introspector.java | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/jdk/src/share/classes/java/beans/Introspector.java b/jdk/src/share/classes/java/beans/Introspector.java index f0ce2a85b81..9001d3516cc 100644 --- a/jdk/src/share/classes/java/beans/Introspector.java +++ b/jdk/src/share/classes/java/beans/Introspector.java @@ -78,20 +78,7 @@ import sun.reflect.misc.ReflectUtil; * 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). - * *

- * 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 ClassLoader - * that has been used to introspect classes, - * you should use the - * {@link #flushCaches Introspector.flushCaches} - * or - * {@link #flushFromCaches Introspector.flushFromCaches} method - * to flush all of the introspected classes out of the cache. - * - *

* For more information about introspection and design patterns, please * consult the * JavaBeans specification.