If I understand what you are asking, my recommendation to you is to not reimplement your data model in your application server. Your data model has already been done for you in Oracle and you are not likely to improve on it. Instead of modeling your data with EJBs, concentrate on modeling your application behavior. Object-orientation is a software design paradigm tuned for application design, not data modeling.
Mike Bresnahan > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]]On Behalf Of Mindaugas Kairys > Sent: Tuesday, April 16, 2002 3:59 AM > To: [EMAIL PROTECTED] > Subject: 3rd normal form & EJB > > > Hello, > I have such philosophical, but real problem. My Oracle admin asks me, why > are you using such plane database design, what will you do, when it will > come the need for new object attributes: alter tables, change > program code, > stop server....? > > I'd wanted to hear opinions, suggestions, the ways you solve that problem > from you and ask what tools, tips, patterns one should use to archieve > database design of 3rd normal form normalization level using EJB? I know > that CMP entity EJB will be solution to achieve that, but it > takes too much > time. Mhm... > > Mindaugas Kairys > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
