Performance depends upon the container implementation. There are ones that
will give your application optimum performance, and there are ones that will
be exceptionally slow. As containers are improved, performance will get
better. And CMP entity beans will be the preferred solution.
> -----Original Message-----
> From: Tom Jordan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 10, 1999 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Persisting Dependant Data
>
>
> 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.
>
> I don't have a problem with modeling dependant data as entity
> beans as it
> provides me with the flexibility of easily mapping it to
> another data store.
> However, would the overhead for this design choice make the
> system perform
> poorly?
>
> I need the flexibility but not at the price of poor
> performance. Let me know
> if you know either way.
>
> Thanks for your input.
> Tom
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.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".
