> -----Original Message-----
> From: Brian N. Miller [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 05, 1999 9:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Granularity of EJBObjects
>
> Someone wrote:
> >
> >I have found that it is best for entity beans to be large/coarse
> >grained components which represent a graph of domain instances. Each
> entity
> >bean has a single root domain object, and the entity represents all
> domain
> >objects referenced from this root.
>
> That would work just fine with Java's default
> serialization-by-reachability,
> but would be painful to map to relational. Hopefully relational storage
> will
> become extinct, but I'm not holding my breath.
>
[Chip Wilson]
Mapping a domain object model to a relational database is always
painful, assuming that the domain model is of high quality. This doesn't
change if entity beans are fine-grained domain objects. The only way to
simplify is to sacrifice your domain and map entity beans to tables, or
sacrifice your relational model and go object dB. I concur with your
assessment of the likelihood of the latter.
> ==========================================================================
> =
> 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".
