Bug report: generate getter/setter method bug

[ydq]

The standard Javabean specification specifies the getter / setter method as follows:

uName -> getuName / setuName

But Lombok generated the code is getUName / setUName

Eclipse: Oxygen Release (4.7.0)
Lombok: v1.16.18

[o-pikozh]

I what place does JavaBeans specification say that a getter should be named getuName instead of getUName?

[cardamon]

Certainly not in section 8.3.1 😉

[Maaartinus]

Duplicate of #1453, #757 and many others.

Javabeans is fubared. Some long time ago I was unhappy about Lombok mistreating my "uShaped" property and wrote manual etters as a workaround. IIRC it didn't work either, because some other tool didn't understand it in the opposite direction (setuShaped -> uShaped), so I ended using "shapedAsU" instead. 🙄

[ydq]

@o-pikozh @cardamon

At least jsp think so...

I use Eclipse to generate getter / setter to keep it correct

Then the jsp show the correct results

[o-pikozh]

@ydq

I already see that it indirectly comes from § 8.8 “Capitalization of inferred names”. It says:

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”

Therefore getABcd ↔ ABcd. So the only remaining way for aBcd is getaBcd. Additionally this is confirmed by:

We provide a method Introspector.decapitalize which implements this conversion rule.

— and Introspector.decapitalize works in that way (aBcd ↔ getaBcd).

Still, you should read the whole discussion. And not duplicate the original report. Probably it will remain "won't fix".

[rzwitserloot]

Duplicate of #2693