"Louth, William (Exchange)" <[EMAIL PROTECTED]>:
> Personally I feel the current bean managed persistence contract is not
> conducive to performance. The performance overhead can be somewhat reduced
> with an object/relational mapping tool such as TopLink. Unless you have
some
> unusual domain model i.e. scientific data and/or a container that does not
> have a good container persistence engine then I would say you would be
> better off with cmp entity beans.
Most persistence engines that automatically generates the SQL (i.e. most
cases of CMP) generally produce silly enough SQL that the database
performance can be significantly increased by using manually constructed SQL
instead, i.e. BMP, even though the transaction management isn't as flexible
with BMP. Having been burnt on CMP more than once, I'm very reluctant to
leave my performance sensitive transactions in the hands of an automagic SQL
generator nowadays.
/Robert
===========================================================================
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".
