Dave Wolf wrote:
> Here is my issue. I agree with much of what you have said until we get into
> passivation. Are you saying that you would find the tradeoff of
> serialization overhead to outweigh the memory overhead of the increased
> number of entity beans? Serialization is a very intensive operation.
Dave,
I believe both you and Avi are confusing what ejbPassivate/ejbActivate do on
entity beans with what they do on stateful session beans. For stateful session
beans, after ejbPassivate is called, the bean is serialized and stored to
some persistent storage (typically, to the file system, perhaps via a database).
For entity beans, however, after ejbPassivate is called, the entity does not
have to be serialized, or stored on disk, or anything else. It simply moves
from the "ready" bin to the "pooled" bin, which is probably a fairly trivial
operation. There should not be any memory or disk overhead associated with a
passivated entity bean, and thus it is certainly not computationally expensive
to passivate.
-jkw
===========================================================================
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".
