So what you're saying is that if I include a separate DTO it doesn't really achieve anything extra - whilst at the same time creating more code to maintain and reducing performance?
Do you know if there is a formal writeup of what is in the blog, something article in a book / report or on a different web site - Google wasn't much help :-( Tim Christopher On Sun, 27 Feb 2005 16:26:35 -0500, Mike Millson <[EMAIL PROTECTED]> wrote: > On Sat, 2005-02-26 at 11:26, Tim Christopher wrote: > > > > I'm also a little concerned that my domain object (Customer.java) is > > also my DTO - is this good practice? > > Take a look at the following article: > http://www.javaperformancetuning.com/news/roundup050.shtml > > I think the author makes a good point. Having a separate DTO class is > like domain persistence, a very odd concept to me. I agree w/ the > author. Pass the domain object as the DTO, not a separate DTO class. > > Mike > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
