When the data model accurately projects the identification of underlying business processes and relationship between the processes then our role(s) becomes one of 'pure implementation' Good Call Larry- M- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its conte ----- Original Message ----- From: "Larry Meadors" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <user@struts.apache.org> Cc: "Martin Gainty" <[EMAIL PROTECTED]> Sent: Monday, October 09, 2006 10:51 AM Subject: Re: FRIDAY #1 JavaBeans/Model
> On 10/9/06, Wesley Wannemacher <[EMAIL PROTECTED]> wrote: >> Wow :) I am really glad you asked that! I actually came to Java >> Development from a DBE background. Normalization is actually one of my >> favorite topics of discussion, and I think this actually stifles my Java >> development from time to time because I tend to think in terms of >> 'normalized db' rather than 'good OO' (I can't be the only one that does >> this). This is likely one of those cases. > > Heh, IMO, OO is a tool, not a goal. > > In 99% of the applications I have worked with/on in the last 20+ > years, the database far outlived any of the applications, because that > is where the true value is. The application is (as are other things > like reporting and data mining tools) simply a tool to access the data > (to extract the value from it). > > My mantra: Get the data model right and it will be easy to make the > application work with it. > > Larry > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
