hi,

> Yeah, entity beans with weblogic 4.51 perform really bad (BEA doen't
> deny, they say you should use tools like toplink for WL)
>
> Our architecture had a workaround to use a session bean and plain
> sql when a lot of "rows" needed to be loaded from the database.  The
> workaround outperformed the entity beans by a considerable factor.

uh but that is a common pattern i would think. loading n rows from the
db via ejbFindByXXX results in at least n+1 queries to the DB (1 to
find the primary keys, n to instantiate the beans). this is clearly
inferior to using a single query and putting the resultset into DAO's
or whatever you might call them.

best regards,
    christian

===========================================================================
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".

Reply via email to