"Database programming with JDBC and Java", O'Reilly
has a pattern that you may find useful. It separates objects
from JDBC classes.
Also check IBM Persistence Builder. It is part of VisualAge for
Java Enterprise. There is a white paper explaining how to map
a class into several tables etc.
http://www7.software.ibm.com/vad.nsf/Data/Document3124?OpenDocument&p=1&BCT=
1&Footer=1
Best regards
Javier Borrajo
I+D Sapin
-----Original Message-----
From: Bengt B�verman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: lunes 3 de mayo de 1999 9:31
Subject: EJB design pattern?
>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".
>
===========================================================================
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".
