Shadi,
First of all to define entity beans for each database table you have
is a pretty bad approach (the least I can say). The need for
entity beans must come from your problem analysis and not from
your DB model.
Try to isolate your objects from your db with views for example and
Data Access Objects (see Sun blueprints or pet store application).
For the second point, the answer is yes but you can achieve the
same goal with CMT.
Loïc
> ----------
> From: SoftFrance MOODAD Shadi[SMTP:[EMAIL PROTECTED]]
> Reply To: A mailing list for Enterprise JavaBeans development
> Sent: Tuesday, February 06, 2001 15:08
> To: [EMAIL PROTECTED]
> Subject: ??SessionBean to Manage Relation between Entity Bean
>
> Hi everybody
>
> I'm trying to map database to object and i'm creating for each table a
> ContainerManaged EntityBean and i implement the relation as cmr field
>
> * but what if -in futur time- i need to implement another relation,
> what if I implement it using a session bean, rather than updating
> the EntityBean,does that cause a problem
>
> * Can a manage transaction manualy from inside a SessionBean, so I
> can do multiple operation on entities like a single operation so
> when I finish I commit or I rollBack
>
> ==========================================================================
> =
> 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".
