When I have a field called e.g. xCoordinate it appears to me that the getter shoud be named getXCoordinate().
Why? Because "get" is clearly a name standard in Java, then "X" and "Coordinate" are distinguishable by the case shift (small x -> big C) so "X" is is clearly the start and end of a word at the same time and should be capitalized.
Now IntelliJ auto-creates a getter called "getxCoordinate". Even though Eclipse does the same, it still appears to me that this is wrong since there is no more distinction between "get" "X" and "Coordinate" rather "getx" forms a non-existing term. Why is this so?
That is related to javabeans specification. Consider a sample below:
It produces the following (notice 'YCoordinate' instead of 'yCoordinate'):
If you are currious why it does this, section 8.8 Capitalization of inferred names of the Javabeans Specification explains it. It's basically to prevent getURL from seeing the property name as uRL.
Here's the section (empahsis added):
When we use design patterns to infer a property or event name, we need to decide what rules to follow for capitalizing the inferred name. If we extract the name from the middle of a normal mixedCase style Java name then the name will, by default, begin with a capital letter.
Java programmers are accustomed to having normal identifiers start with lower case letters. Vigorous reviewer input has convinced us that we should follow this same conventional rule for property and event names.
Thus when we extract a property or event name from the middle of an existing Java name, we normally convert the first character to lower case. However to support the occasional use of all upper-case names, we check if the first two characters of the name are both upper case and if so leave it alone. So for example,
“FooBah” becomes “fooBah”
“Z” becomes “z”
“URL” becomes “URL”
We provide a method Introspector.decapitalize which implements this conversion rule.