Can you elaborate on the disadvantage of option 3? This is
in fact how Sun suggests implementing entity beans in the spec.
> -----Original Message-----
> From: Dogadin Dimitri [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 15, 2000 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: Entity bean question
>
>
> We have a review entity. This entity consists of review table and 3
> "reference" tables. In the reference tables we keep
> information related to
> the specific type of review. There can more than one
> reference record per
> one review.
>
> We think to represent this entity as an entity bean. We came up with
> several ways to do that.
>
> 1. Represent this as 3 entity beans wrapped in Stateful
> Session Bean.
> Entity Beans are container managed. There is an article in
> JDJ(June 2000, page 126) that does not recommend to use CMP
> for entity bean
> that has more than one table and several records.
>
> 2 The same as 1, but use bean managed persistence
> instead of CMP.
>
> 3. Represent it as one huge entity bean.
> Disadvantage of this: Adding new review
> types or modifying
> old types.
>
> 4. Not to use entity bean at all. Use a bunch of
> stateless bean calls.
>
>
>
> Thanks in advance for suggestions
>
> Dimitri Dogadin.
>
> Britannica.com
>
> ==============================================================
> =============
> 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".
