Imre
Imre Kifor wrote:
> >The activation/passivation for session beans comes in handy here. You just
> >de-activate a session instead of expire it.
>
> Sorry to disappoint you again, but neither the client nor the bean instance
> can activate/deactivate/expire a session object. These operations are up to
> the container.
I quite aware of this and neither client nor the bean instance need to be in
control of the deactivation/reactivation.
> And the container has to manage resources, so an expiration
> needs to be an expiration.
Yes, the container manages resources. Once a session bean is deactivated is
lives on secondary storage, usually there's plenty of that. Eventually the
container will expire a session bean, i.e. removes it from secondary storage.
That's a nice two-level resource management approach.
I expect a good container to provide APIs for managing the deactivation
policies (even though it's part of the spec - but the whole area of
adminstration is very lightly addressed anyway.)
Cheers,
Andreas
--
"Programming with Enterprise JavaBeans, JTS and OTS" is now available. Collect
all three!
www.wiley.com/compbooks/vogel
===========================================================================
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".
