Head First EJB

Even the methods that are the same, don’t behave the same

SessionBean interface		EntityBean interface
setSessionContext(SessionContext sc)		setEntityContext(EntityContext ec)
	Container gives the bean a reference to its context.		Container gives the bean a reference to its context.
ejbPassivate()		ejbPassivate()
	Called on a stateful session bean, when the bean is about to be serialized (or something like it).		Called when the bean is about to return to the pool, following a transaction.
ejbActivate()		ejbActivate()
	Called on a stateful session bean, when the bean is reactivated following passivation (might be deserialization).		Called when the bean is taken out of the pool to service a client’s business method call.
ejbRemove()		ejbRemove()
	Called on a stateful bean when the client calls remove(). Called on a stateless bean when the Container wants to reduce the size of the pool.		Called when the client calls remove(), and wants to delete this entity from the database!
		unsetEntityContext()
			Called when the Container wants to reduce the size of the pool.
		ejbLoad()
			Called when the bean has been refreshed with data from the underlying persistent store.
		ejbStore()
			Called when the Container is about to update the

Note

Of the four methods that are in both SessionBean and EntityBean, only the context setter method behaves the same way! In an entity bean, activate, passivate, and remove are completely different from a session bean

Note

EntityContext adds getPrimaryKey()

Both SessionContext and EntityContext ...