Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of
 lists+1214986160035-208411@n2.nabble.com designates 216.139.236.158 as
 permitted sender)
Message-ID: <1236622144759-2450634.post@n2.nabble.com>
Date: Mon, 9 Mar 2009 11:09:04 -0700 (PDT)
From: is_maximum <mnrz57@gmail.com>
To: users@openjpa.apache.org
Subject: Re: What is ManagedInterface
In-Reply-To: <ACE7FF24-C4A1-41B8-AE96-C15F22F22C6E@SUN.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <1236606317654-2449023.post@n2.nabble.com>
 <ACE7FF24-C4A1-41B8-AE96-C15F22F22C6E@SUN.com>


Thanks Craig,
Yes it reduces the redundant code. But I was thinking of a great idea behind
that which may leads me to a revolution in my application :)


Craig L Russell wrote:
> 
> Hi is_,
> 
> On Mar 9, 2009, at 6:45 AM, is_maximum wrote:
> 
>>
>> Hi
>>
>> Can anyone explain what is the ManagedInterface good for? What  
>> benefit would
>> achieve if we define all of our entities as interfaces?
> 
> If your entities are pure data (no behavior) then defining them as  
> interfaces reduces mindless code generation for the implementation of  
> get and set methods. All you do is declare the methods and OpenJPA  
> does the rest.
> 
> Craig
>>
>>
>> thanks
>> -- 
>> View this message in context:
>> http://n2.nabble.com/What-is-ManagedInterface-tp2449023p2449023.html
>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>
> 
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
> 
> 
>  
> 

-- 
View this message in context: http://n2.nabble.com/What-is-ManagedInterface-tp2449023p2450634.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.