Ken,
A stateful session bean is _not_ supposed to save its own state when it is
passivated. The container is responsible for saving its state. If your
application requires that your session state be recoverable following a
container crash, then you need to select an app server that provides this
type of recoverability.
Recoverability capabilities of stateful session beans is an area of vendor
differentiation. The spec says that stateful session beans are not
necessarily recoverable. Certain vendors provide an option to store session
state in a database to ensure session state recoverability.
(Vendors: I'd like to take a tally -- please send me private mail and let me
know if you offer this feature. Thanks!)
Anne
-----Original Message-----
From: Kenneth D. Litwak [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 04, 1999 11:54 AM
Subject: Passivation and EJB restrictions
If EJBs are not supposed to do file I/O, but stateful session beans should
sae
their state in a persistent store when they are passivated (which I believe
is
because the container might crash while the bean is passivated, though it it
is
written to secondary storage by the container I don't see the need -- what
is up
with this?), then how is the session bean supposed to sae iuts state?
Unless
the requirement is to use a database,which would be rather onerous I think,
there is a conflict here between what you should do to passivbate a bean and
what you're not suppose dto do. How is this supposed tobe resolved?
Thanks.
Ken
===========================================================================
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".
