introduce property to make caching optional

[Bob426]

Is your feature request related to a problem? Please describe.

In version 2.8.11, a caching mechanism was introduced to improve performance. The relevant commit is as follows: #3065.
We use a CustomModelResolver to fix the problem described here #3110, among other things. Our solution is that we can use reflection for each field and object through Jakarta Annotation to determine whether it is nullable or not. However, caching means that it is no longer necessary to iterate through each field with reflection, which is why our logic no longer works. Everything still worked in the old version 2.8.10.

Describe the solution you'd like
We would like to have an option to disable caching so that we have the old behavior as in 2.8.10.

Describe alternatives you've considered

no suitable alternative found

Additional context

no additional context

[Mattias-Sehlstedt]

A bit outside the questions, but would defining a PropertyCustomizer change (fix) the behavior of parsing annotations?

An example can be seen in this test. Depending on your scope of customization it could be an easier definition than customizing an entire ModelResolver.

[Bob426]

I will try out, if a property customizer is good alternative, thanks for the hint. I will give you feedback

[Bob426]

I tried using PropertyCustomizer, but unfortunately I have some more complex customizations where I need to make recursive changes, which I can only get to work with PropertyCustomizer by taking a lot of detours. But as you said, PropertyCustomizer doesn't solve my caching problem. It would be nice if the caching mechanism could be enabled and disabled optionally.