A session object
Jump to navigation
Jump to search
A typical session object has the following characteristics:
- Executes on behalf of a single client.
- Can be transaction-aware.
- Updates shared data in an underlying database.
- Does not represent directly shared data in the database, although it may access and update such data.
- Is relatively short-lived.
- Is removed when the EJB container crashes. The client has to re-establish a new session object to continue computation.
A typical EJB container provides a scalable runtime environment to execute a large number of session objects concurrently. The EJB specification defines both stateful and stateless session beans. There are minor differences in the API between stateful session beans and stateless session beans.