Where and in what format stateful session state is stored is an implementation detail of the container.
In many cases passivation will not take place at all, so the session bean state is simply stored in
memory between invocations.If passivation does take place, the container is allowed to store the
passivated state anywhere it likes. Many implementations provide configuration that determines where
the state is stored.In SUN's implementations, the deployer can choose between a file system store,
a high availability database, or in-memory replication.
The important thing is that the application code does not have to concern itself with most of these
details.All you need to do as a developer is ensure that the bean class state conforms to the
contracts for Serializability.The exact rules are covered in Section 4.2.1 of the EJB 3.0 spec.
--ken