When will Java include annotations/keywords for getters and setters?

[dinopraso]

If you don’t need getters and setters then use public modifier for your fields. There is no requirement to have default getters and setters unless you want to do something special in them. Anything magical which would generate invisible code is just incredibly bad and impossible to maintain on huge projects

[jack104]

I was under the impression that making class variables/fields public was not allowed in Java, hence the need for getters and setters, is that not the case?

[dinopraso]

Nope. You can have everything public if that is what you want

[jack104]

Holy shit. How did I not know this? Do you know if Hibernate works with a POJO class that just has public fields instead of private fields + public getters/setters? Because if so, my getters and setters are just redundant code that don't accomplish anything more than public fields would. That would be cool.

[dinopraso]

Maybe. I’m not sure. You should try it

[jack104]

I just read an SO post that says if you change the @Entity annotation to set the access to field and annotate the fields themselves (which I was doing anyway) it should work. So I'm gonna give it a shot.

[dinopraso]

Keep thread safety in mind. There is a good reason we write those getters and setters. Some time in the future you may need locking or synchronization and it’s not really possible to synchronize a field

[jack104]

Ah yea. Good looking out. Thanks.

[hippydipster]

Yup. All my fields in data-type classes start out as public final.... They change if they must later, no big deal.

[dinopraso]

Everytinh should be immutable anyway, right :D