Dave Wolf wrote:
> But there is one major difference. For the entity bean finder you will have
> N (n=rows) instances of an entity bean (and possible N*users) in memory for
> every row. Whereas one stateless session bean may be able to service
> multiple users and does not need one instance for every row. Each instance
> is a space in memory.
>
So what? If you load the state yourself, you'll also have to create an array or
a collection of something, no? And these somethings will also use space in
memory. At least entity bean instances are cached and pooled by the server.
On the other hand, coding the finder yourself will more or less break the EJB
model and will force you to write JDBC code yourself, which is error-prone and
costs money. Hardware is cheaper than developers.
JB.
>
> IMHO I always use a session bean to find and an entity bean to change.
>
> Dave Wolf
> Internet Applications Division
> Sybase
>
<deleted>
--
Jean-Baptiste Nizet
[EMAIL PROTECTED]
R&D Engineer, S1 Belgium
Kleine Kloosterstraat, 23
B-1932 Sint-Stevens Woluwe
+32 2 200 45 42
===========================================================================
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".
