Comments on: Hibernate and your Getters and Setters http://www.missiondata.com/blog/software-development/67/hibernate-and-your-getters-and-setters/ Louisville-based Web Development & Software Engineering Tue, 02 Mar 2010 02:10:53 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Sami Dalouche http://www.missiondata.com/blog/software-development/67/hibernate-and-your-getters-and-setters/comment-page-1/#comment-52179 Sami Dalouche Tue, 19 Feb 2008 21:23:35 +0000 http://www.missiondata.com/blog/uncategorized/67/hibernate-and-your-getters-and-setters/#comment-52179 sorry, I repeat If you consider the DDD (Domain Driven Design) approach a good one, then I don’t believe that breaking encapsulation really is an issue. Indeed, if you consider that your entities constitute a rich domain, then you might not even want setters, you might want a fluent interface to set your parameters, etc.. So, Entities can be created by factories and persisted using Repositories. I think it is way better to have stronger encapsulation on the domain and break it in the factories and repositories, instead of having a weaker encapsulation that is not broken anywhere. So, in this direction, direct field access doesn't seem stupid sorry, I repeat

If you consider the DDD (Domain Driven Design) approach a good one, then
I don’t believe that breaking encapsulation really is an issue.

Indeed, if you consider that your entities constitute a rich domain, then you might not even want setters, you might want a fluent interface to set your parameters, etc..

So, Entities can be created by factories and persisted using Repositories. I think it is way better to have stronger encapsulation on the domain and break it in the factories and repositories, instead of having a weaker encapsulation that is not broken anywhere.

So, in this direction, direct field access doesn’t seem stupid

]]> By: at Obscured Info http://www.missiondata.com/blog/software-development/67/hibernate-and-your-getters-and-setters/comment-page-1/#comment-16214 at Obscured Info Mon, 12 Mar 2007 02:17:40 +0000 http://www.missiondata.com/blog/uncategorized/67/hibernate-and-your-getters-and-setters/#comment-16214 [...] Over at the MD blog Darren has illustrated more dangers with Hibernate setters. [...] [...] Over at the MD blog Darren has illustrated more dangers with Hibernate setters. [...]

]]> By: Rich Rodriguez http://www.missiondata.com/blog/software-development/67/hibernate-and-your-getters-and-setters/comment-page-1/#comment-16213 Rich Rodriguez Mon, 12 Mar 2007 00:28:39 +0000 http://www.missiondata.com/blog/uncategorized/67/hibernate-and-your-getters-and-setters/#comment-16213 I'm pretty satisfied using access="field" with Hibernate. Yes, it breaks encapsulation, but it keeps you from running into these maddening bugs. I <a href="http://www.obscured.info/java/my-setter-is-too-clever-or-why-hibernate-isnt-batching/" rel="nofollow">blogged</a> a while back about how setter logic was defeating the batch load functionality in Hibernate. I’m pretty satisfied using access=”field” with Hibernate. Yes, it breaks encapsulation, but it keeps you from running into these maddening bugs. I blogged a while back about how setter logic was defeating the batch load functionality in Hibernate.

]]>