Adena Galinsky wrote:
>
> Hi everyone,
> Everything I've been reading seems to indicate that calling the find methods
> in entity beans just wastes time and resources. They seem to recommend
> writing find methods in session beans, which issue JDBC calls directly and
> return an array of primary keys. Given that this is faster and lighter
> weight, why would we ever write a find method in an entity bean which
> returns more than one instance of a bean?
Because your server might (and in the future, many servers will) support
caching of entity beans and finder methods such that the entity bean approach
scales better than the session bean/JDBC approach.
If you are currently using a server for which caching options are limited,
you may well find the session bean approach scales better (for now).
> -Adena
>
> ===========================================================================
> 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".
--
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
