Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 70235 invoked from network); 28 Feb 2005 15:23:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Feb 2005 15:23:13 -0000 Received: (qmail 21226 invoked by uid 500); 28 Feb 2005 15:22:35 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 21184 invoked by uid 500); 28 Feb 2005 15:22:34 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 21168 invoked by uid 99); 28 Feb 2005 15:22:34 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of tim.christopher@gmail.com designates 64.233.184.192 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.192) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 28 Feb 2005 07:22:33 -0800 Received: by wproxy.gmail.com with SMTP id 36so1019018wra for ; Mon, 28 Feb 2005 07:22:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=obcDD+xQr3K/d1OXDlRrU6zl8rioWUu4W15cAqL0TkIGAc2TwB4QFfpwkbeMGCdhDhsH6hQa/Bnmta6Lht5YCbb+UGGqTZqz8Vsq00S+jsjl53+JsrVb1c3pqPmxGjng/k+9jlof4VSdW8LKvfQZnVHXp/Eql8Pj3VD/NHgnYgE= Received: by 10.54.47.27 with SMTP id u27mr19087wru; Mon, 28 Feb 2005 07:22:28 -0800 (PST) Received: by 10.54.28.22 with HTTP; Mon, 28 Feb 2005 07:22:28 -0800 (PST) Message-ID: <63394b5205022807225e3690ce@mail.gmail.com> Date: Mon, 28 Feb 2005 15:22:28 +0000 From: Tim Christopher Reply-To: Tim Christopher To: Struts Users Mailing List Subject: Re: AW: Struts Approach Cc: mmillson@meritonlinesystems.com In-Reply-To: <1109539594.26447.24.camel@alex.meritonlinesystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <422072dd.30cef84b.56d2.661fSMTPIN_ADDED@mx.gmail.com> <63394b5205022608262482dbb6@mail.gmail.com> <1109539594.26447.24.camel@alex.meritonlinesystems.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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 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: user-unsubscribe@struts.apache.org For additional commands, e-mail: user-help@struts.apache.org