Create rules for bean property determination

[jmle]

According to the migration guide:

The core container performs basic bean property determination without java.beans.Introspector by default. For full backwards compatibility with 5.3.x in case of sophisticated JavaBeans usage, specify the following content in a META-INF/spring.factories file which enables 5.3-style full java.beans.Introspector usage: org.springframework.beans.BeanInfoFactory=org.springframework.beans.ExtendedBeanInfoFactory

Investigate and create rules if necessary.

In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[jmle]

In Spring 5 and earlier versions, Spring relied on java.beans.Introspector for certain advanced cases of bean handling, such as working with custom BeanInfo implementations or handling non-standard JavaBeans. This allowed Spring to analyze a bean’s properties using the introspection mechanisms provided by the JavaBeans API.

This rule could look for BeanInfo implementations or usage. Maybe make it a potential rule. The solution is simple, just follow the migration guide and add the config.