1st, is it considered bad form to hold onto an entity bean as an ivar of
a statefull session bean.
For example if I have a session bean that does a lot of interaction with
an entity bean, it might save time to just hold onto it.
2nd, if it isnt bad form, or if I wanted to do it anyway, how would the
pasivation of the session bean work.
For example, I create a session bean A, it gets a reference to entity
bean B (which is persistent to a RDBMS).
When the server wants to passivate A (say its getting full up), it
serializes it, and all of its references. Does this mean it will also
serialize the Entity bean? Or is it smart enough to remember how to just
re-find the entity bean , and let it passivate itself.
I guess the concern here, is it possible to have a entity bean
serialized to disk and in the rdbms. If so, it seems like this could
cause problems.
thanks
Joel
===========================================================================
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".
