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".
