On Fri, 10 Dec 1999, Tom Jordan wrote:
> David,
>
> Thanks for your input but you are providing two contradictory points:
>
> >Dependent objects should not be modeled as entity beans. Personally, I
> >would just make OrderLineItems into entity beans
> >because I want to avoid handwriting SQL and I don't want to use an O/R
> >tool.
What I meant to say (it didn't come out too clearly) is that the general rule
of thumb as determined by this mailing list is not to model dependent objects
as entity beans. That said, I personally feel that I would pay the performance
price of modeling dependent objects as entity beans in order to speed up
development and make maintenance easier.
Then, of course, once the system is done and performance tuning begins, if this
area turns out to be a bottleneck, it could be redeveloped using bean-managed
persistence and hand coding of SQL to get the necessary speed.
> However, would the overhead for this design choice make the system perform
> poorly?
I don't know in practice how it would turn out in your situation.
cheers,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.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".
