We are currently in the middle of designing a system using EntityBeans, with
bean managed persistence, to describe our core bussines logic. As all these
business objects' data already resides in a relational database that is
normalized and not looking like objects in a table we cannot use the simple
schemas of CMP.
My question is if there are any good patterns for separating the core
business objects from their data representation stored in the database. I
imagine two classes, say Horse and HorseData. Is there a good pattern for
this separation preferable with a rather loose coupling.
Thank you in advance!
Bengt Baverman
[EMAIL PROTECTED]
===========================================================================
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".
