Browse Source
Prior to this commit, `ClassUtils#forName` would always attempt to resolve the given class name as a nested type. For example, searching for `org.example.Spring` would try to resolve: * `org.example.Spring` * if not available, try `org.example$Spring` as well Java classes usually start with uppercase letters, so this additional lookup can be costly and not very useful. This commit only attempts nested class lookups when the previous segment starts with an uppercase. So `org.example.Spring.Issue` will look for `org.example.Spring$Issue`, but `org.example.Spring` will not. Closes gh-31258pull/31279/head
1 changed files with 2 additions and 1 deletions
Loading…
Reference in new issue