A session object: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''A typical session object has the following characteristics:''' |
'''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. |
|||
---- |
---- |
||
| Line 12: | Line 12: | ||
objects concurrently. |
objects concurrently. |
||
The EJB specification defines both stateful and stateless session beans. There are minor differences in |
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. |
the API between [[stateful session beans]] and [[stateless session beans]]. |
||
Latest revision as of 17:20, 19 November 2004
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.