This question is similar to Strange autogenerated getter and setter in eclipse, but I don't find a proper answer for me there or into the linked questions.
Say I have this class. Pay attention on capitalization:
public class Foo {
private String xxxxx;
private String yYyyy;
private String zzZzz;
}
From my point of view, it follows naming conventions, since all attributes begin with a lowercase letter. So I expect Eclipse to autogenerate these getters and setters:
getXxxxx()...
setXxxxx(String xxxxx)...
getYYyyy()...
setYYyyy(String yYyyy)...
getZzZzz()...
setZzZzz(String zzZzz)...
But Eclipse autogenerator does this instead (pay attention to yYyyy getter/setter differences):
getXxxxx()... // Ok
setXxxxx(String xxxxx)... // Ok
getyYyyy()... // Different!
setyYyyy(String yYyyy)... // Different!
getZzZzz()... // Ok
setZzZzz(String zzZzz)... // Ok
Ok, so my guess is: "Naming convention forbids an attribute to begin with a lowercase letter followed by an uppercase one. You need at least 2 lowercase letters.".
My questions are:
1) Is this assumption OK? If yes, why is it that way?
2) Why does Eclipse behave like that on "yYyyy" case? If we assume that the attribute naming is not OK, it seems to me that Eclipse makes it even worse. Is it a bug? Is there any reason for that?
Thanks.
