Developing EJBs (continued)... Session Beans
Execute on behalf of a single client and is an extension of the client that created it
They may or may-not be transaction-aware
They may or may-not update data in the underlying database
Their lifetime is limited to that of the client and hence they are relatively short-lived
They do not survive server crashes
They do not represent data in the database
Since they only represent conversational state with a single client, their identity is hidden