[
https://issues.apache.org/jira/browse/BEANUTILS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466175#comment-17466175
]
Sébastien Lepage edited comment on BEANUTILS-552 at 12/28/21, 5:14 PM:
-----------------------------------------------------------------------
PR: [https://github.com/apache/commons-beanutils/pull/104]
One mistake I might be doing, is to exclude class property by setting
Object.class as a stopClass...
was (Author: JIRAUSER282553):
PR: [https://github.com/apache/commons-beanutils/pull/104]
One mistake I might be doing, is to exclude class property setting Object.class
as a stopClass...
> Allow stopClass for PropertyUtilsBean
> -------------------------------------
>
> Key: BEANUTILS-552
> URL: https://issues.apache.org/jira/browse/BEANUTILS-552
> Project: Commons BeanUtils
> Issue Type: Improvement
> Components: Bean / Property Utils
> Affects Versions: 1.9.3
> Reporter: Sébastien Lepage
> Priority: Major
>
> By default, DefaultBeanIntrospector is used as introspector. Turns out, I
> need to set a stopClass during introspection. Instead of removing
> DefaultBeanIntrospector instance and then add a new one. I would like to set
> my very own introspectors in ctor. I can see from the latest version that
> PropertyUtilsBean#resetBeanIntrospectors exclude by default class property
> using SuppressPropertiesBeanIntrospector, I have two suggestions, either:
> * DefaultBeanIntrospector uses Object as a stop class
> * Define a StopClassBeanIntrospector allowing to define a stopClass (or add
> a new method getStopClass into IntrospectionContext and by default returns
> Object.class, no breaking change)
> * Or having both?
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
