By rick
via oracle.com
Published: May 31 2008 / 14:32
-
Why Node.js is awesome: A short history of web applications
-
Mozilla Antarctica community site launched by coolest Firefox fans
-
Contexts and Dependency Injection in Java EE 6: @EJB vs @Inject
-
Ubuntu 12.04 ARM Performance Becomes Very Compelling
-
Neo4j App Performance Profile Management using New Relic
-
Let’s Make a 3D Game with HTML5
Comments
Jakob Jenkov replied ago:
I must say, that I disagree with the articles argument about annotating fields rather than getters and setters. By using getter / setter annotation you can specify that a field is to be read from DB (annotate the setter), but never written (don't annotate getter). You can also split a db-field into two fields inside a setter, and join two object fields into one in a getter. In general I personally find using getters / setters a much more flexible mechanism when working with persistence.
Voters For This Link (22)
Voters Against This Link (0)