Hi Steve Ebersole, I had a look into your suggestion, yet using a switch is not possible: because of legacy, some of this code is in static blocks and I have no access to the configuration properties.

People shouldn't rely on class names as an integration contract; we can change the current naming strategy to make things simpler between 5.0/5.1/5.2/5.3 compatibility - especially for the Spring devs - but I'd also make it clear that such naming patterns are not a future-proof promise.

If anyone has a suggestion on how a better API would looke like - something like Helper.isProxy(obj) - then we could add that but I'd need to the Spring team to confirm if they'd actually use it and how it should look like exactly before adding such a thing.

For now, I propose I just change the naming scheme: w/o configuration settings nor logs. KISS