Modelling using Session & Entity Beans
Use Session Beans for Application logic
Use Session Beans as the only interface to the client
Expect little reuse of session beans
Use session beans to control the workflow of a group of entity beans
Use Entities to develop a persistent object model (wrap all yr. JDBC code)
Use Entities to enforce accuracy/integrity of your database
Insist on reuse of entities
To model domain objects with a unique identity shared by multiple clients