The property resolution in custom repository queries fails if the property name starts with a single lowercase letter followed by an uppercase letter. The following entity and repository demonstrate the problem:
In Spring Boot version 2.1.8.RELEASE (includes spring-data-commons 2.1.10.RELEASE) the code above was working but in version 2.1.9.RELEASE (includes spring-data-commons 2.1.11.RELEASE) the following exception was thrown:
Looks like you're running into a side-effect of the fix for DATACMNS-1570. It might be surprising – it definitely is to me – but according to the Java Beans specification the expected getter method name is getcLoginId.
The documentation states that the first character of the property is decapitalized therefore the former example should still work.
Actually, I can't find that in the section you linked. We don't state any details except "uncapitalized" which I guess we can improve on by replacing it with "converted ac cording to the Java Beans specification"
I was referring to the statement "... checks the domain class for a property with that name (uncapitalized).". I have interpreted the word "uncapitalized" as "the first character of the property is decapitalized" which was the original behavior as well.
getcLoginId feels some kind of weird although adhering to the Java Beans specification is the correct way IMO.
I would appreciate if you would explicitly mention this detail in the linked documentation, as this would have helped a lot in the first place