<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Avoiding anemic domain models with Hibernate</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Sat, 25 May 2013 00:29:07 -0400</pubDate>


    <item>

        <title>forced public EJB CMP getters</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=31010</link>

        

        
            <description><![CDATA[<div class="jive-quote"><div class="jive-quote">EJB CMP forces you to make all your accessors public<br><br>as far I am using EJB CMP I think I have to correct the statement above:<br><br>yes, it is right that all persistent fields are represented by...]]></description>
        

        <pubDate>Mon, 08 Aug 2005 16:19:27 -0400</pubDate>

        

        <jf:creationDate>Mon, 08 Aug 2005 16:19:27 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 08 Aug 2005 16:19:27 -0400</jf:modificationDate>
        <jf:date>Aug 8, 2005</jf:date>
        <jf:author>Hans Prueller</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>The flaw of Anemic Domain Model</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=31010</link>

        

        
            <description><![CDATA[<blockquote>I'm not sure from reading this piece what the flaw is in having domain objects that lack intelligence. The purpose of the domain objects is to model out entities in the world. Separating out &lt;strong&gt;how we act upon these...]]></description>
        

        <pubDate>Thu, 26 May 2005 13:03:04 -0400</pubDate>

        

        <jf:creationDate>Thu, 26 May 2005 13:03:04 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 26 May 2005 13:03:04 -0400</jf:modificationDate>
        <jf:date>May 26, 2005</jf:date>
        <jf:author>Jing Xue</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Exactly the point</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=31010</link>

        

        
            <description><![CDATA[This is not about DAOs. DAOs are just for reading/writing data and should be &quot;dumb&quot; with respect to business logic, rather should be there to service requests for information from a business layer. <br><br>I'm not sure from reading this piece...]]></description>
        

        <pubDate>Thu, 12 May 2005 17:39:27 -0400</pubDate>

        

        <jf:creationDate>Thu, 12 May 2005 17:39:27 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 12 May 2005 17:39:27 -0400</jf:modificationDate>
        <jf:date>May 12, 2005</jf:date>
        <jf:author>John Kelvie</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re:DAOs are an anti-pattern?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=31010</link>

        

        
            <description><![CDATA[That is the impresion I get.  On the other hand there is still a lot of data access stuff that goes specific to hibernate that would normaly fall into a DAO.  Let's say you wanted to be able to swap out Hibernate, a well architected system would let you...]]></description>
        

        <pubDate>Wed, 16 Mar 2005 23:04:17 -0500</pubDate>

        

        <jf:creationDate>Wed, 16 Mar 2005 23:04:17 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 16 Mar 2005 23:04:17 -0500</jf:modificationDate>
        <jf:date>Mar 16, 2005</jf:date>
        <jf:author>Adam Lewis</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>DAOs are an anti-pattern?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=31010</link>

        

        
            <description><![CDATA[From what I can tell, it sounds like DAOs are basically anti-patterns then since they do all the transactional script stuff outside of the actual entity.  Am I understanding this correctly?]]></description>
        

        <pubDate>Tue, 01 Mar 2005 02:26:41 -0500</pubDate>

        

        <jf:creationDate>Tue, 01 Mar 2005 02:26:41 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 01 Mar 2005 02:26:41 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2005</jf:date>
        <jf:author>Archimedes Trajano</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Avoiding anemic domain models with Hibernate</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=31010</link>

        

        
            <description><![CDATA[The pattern itself is trivial: if you don't want other objects to access a field in a persistent object directly to preserve some invariant condition, you can put business logic to check that condition right in the persistent object and then have...]]></description>
        

        <pubDate>Sun, 09 Jan 2005 08:45:12 -0500</pubDate>

        

        <jf:creationDate>Sun, 09 Jan 2005 08:45:12 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 09 Jan 2005 08:45:12 -0500</jf:modificationDate>
        <jf:date>Jan 9, 2005</jf:date>
        <jf:author>Bill Schneider</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>



</channel>
</rss>

