Ah yes, good point.  I’ll go ahead and do that before we release tomorrow.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wouter Zoons
Sent: Saturday, December 25, 2004 6:59 PM
To: 'Chad Brandon'; [email protected]
Subject: RE: [Andromda-devel] spring dao transform

 

What I meant was: the default impl now returns the entity itself (in the DAO impl) .. we could easily move that into the DaoBase and let the user override if he wants (that way the Impl only contains code the user actually needs to see)

 


From: Chad Brandon [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 26, 2004 1:49 AM
To: [EMAIL PROTECTED]; [email protected]
Subject: RE: [Andromda-devel] spring dao transform

 

What exactly would the default implementation be?  If you’re doing exact copies of the value objects to entities then yes it would make sense, however I haven’t implemented that option because usually my value objects aren’t one to one (or isomorphic).  If they were isomorphic, you might as well return the entity most of the time.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wouter Zoons
Sent: Saturday, December 25, 2004 2:30 PM
To: [email protected]
Subject: [Andromda-devel] spring dao transform

 

Hi Chad,

 

I was wondering why the transformEntity() methods in the DAOImpl classes are abstract in the DAO base classes .. why don’t they have the default implementation in the DAO base and isn’t there a comment or something in the impl. indicating you can override in the DAO impl if desired ?

 

Unless I am overseeing something here, I think it makes sense to do so

 

-- Wouter

 

Reply via email to