According to spec, for SFSB, after ejbPassivate(), if there are still some fields not meet the requirements of serialization, the container may choose to destroy the bean instance, so if the clients try to invode the business method on this bean, client gets a ObjectNotFoundException, isn't it ?
SCJP, SCWCD, SCBCD, SCDJWS, OCA9i,<br />IBM Certified WAS5.0 Admin<br />IBM Certified Solution Developer - WebSphere Studio 5.0<br />IBM Certified Solution Developer - XML and related Technologies
You are correct in stating that the sfsb is destroyed if the container could not passivate it.
However, when the client invokes a biz method on the bean's component interface (after the bean is destroyed) it will get a system exception rather than javax.ejb.ObjectNotFoundException (which is an application exception thrown from entity bean's single finder methods when an entity with the specified attributes cannot be found in the underlying persistence store):
* java.rmi.NoSuchObjectFoundException - remote clients will get this system exception OR * javax.ejb.NoSuchLocalObjectFoundExceptio - local clients will get this system exception