----- Original Message -----
From: "Geert Mergan" <[EMAIL PROTECTED]>
> Another major concern regarding performance is finder methods.
> If you need to load say thousands of entity beans from the database,
> how does the spec say the container should do it: row per row or all rows
> at once? If it loads them row by row then entity beans are no good
> in scenarios where you often need to load lots of entity beans.
AFAIK, this is the *only* real problem with Entity Beans and it is limited to
Bean Managed Persistence only. The EJB 2.0 spec will introduce the concept of a
persistence manager, and this should allow the developer to circumvent that
limitation. We can only hope. ;-)
As far as the OO arguments earlier, I have another point. I have a rich OO model
and I use entity beans. The way to achieve this is to keep your OO in Value
Objects. Entity Beans encapsulate these value objects, persist them and still
benefit from the business logic.
jim
===========================================================================
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".
