BeanInfoFactory implementation that performs standard
java.beans.Introspector inspection.
To be configured via a META-INF/spring.factories file with the following content:
org.springframework.beans.BeanInfoFactory=org.springframework.beans.StandardBeanInfoFactory
Ordered at Ordered#LOWEST_PRECEDENCE to allow other user-defined
BeanInfoFactory types to take precedence.
ExtendedBeanInfoFactory, CachedIntrospectionResults, Introspector#getBeanInfo(Class)
| Modifier and Type | Field and Description |
|---|---|
| public static final String | IGNORE_BEANINFO_PROPERTY_NAME
System property that instructs Spring to use the |
| private static final boolean |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public BeanInfo | getBeanInfo(Class<?>
the bean class beanClass)Implements org. Return the bean info for the given class, if supported. |
| public int |
| IGNORE_BEANINFO_PROPERTY_NAME | back to summary |
|---|---|
| public static final String IGNORE_BEANINFO_PROPERTY_NAME System property that instructs Spring to use the The default is "false", considering all Note that such an effect may also indicate a scenario where caching doesn't work
effectively: Prefer an arrangement where the Spring jars live in the same ClassLoader
as the application classes, which allows for clean caching along with the application's
lifecycle in any case. For a web application, consider declaring a local
| |
| shouldIntrospectorIgnoreBeaninfoClasses | back to summary |
|---|---|
| private static final boolean shouldIntrospectorIgnoreBeaninfoClasses | |
| StandardBeanInfoFactory | back to summary |
|---|---|
| public StandardBeanInfoFactory() | |
| getBeanInfo | back to summary |
|---|---|
| public BeanInfo getBeanInfo(Class<?> beanClass) throws IntrospectionException Implements org. Doc from org. Return the bean info for the given class, if supported.
| |
| getOrder | back to summary |
|---|---|
| public int getOrder() Implements org. Doc from org. Get the order value of this object. Higher values are interpreted as lower priority. As a consequence,
the object with the lowest value has the highest priority (somewhat
analogous to Servlet Same order values will result in arbitrary sort positions for the affected objects.
| |