Re: when a table should be represented as Entity Bean?

[Matthew Hixson]

Hi Manoj,
  If I were implementing this I would implement the LineItems as their
own entity bean.  Especially if I were doing this with CMP.  The reason
being that the container would be handling the relationships and
reading/writing of both Orders and LineItems.
  If you leave the LineItems as helper classes then you're responsible
for storing those in the database yourself.
  -M@

On Saturday, January 11, 2003, at 03:40 AM, Manoj Kumar wrote:

Hi,
   While designing the EJBs, a table can be represented as a Entity
bean
and it could also be represented by just a helper class. e.g If i have
a
Order table and a LineItem table and there is a one to many
relationship
between the two tables. In my design i have represented them as two
seperate entity beans. However, LineItems could also be represented as
a
helper class, instead of making it a Entity bean.What are the
guidelines, which tells that when a table should be represented as a
entity bean and when it should be a helper class???

Thanks
Manoj

=======================================================================
====
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".