Session beans can definitely persist data. However, typically they are being used as a
method of implementing business processes for the client. What this means is that by
invoking a method on a session bean, you can have many other entity beans join the
transaction. If the transaction as a whole succeeds/fails all of the changes to the
entities are commited/rolled back. This is obviously a better mechanism than using
UserTransaction. Thus, sessions can be used as an outer layer to wrap many small
entity transactions into one atomic transaction.
Stateful session beans are typically used to collect state, and then perform a
transaction with a combinations of entities and the collected state. Stateless are
typically being used to transact across a set of entities.
Just my 2 cents.
--Chris.
---------- Original Message ----------------------------------
From: Cedric Beust <[EMAIL PROTECTED]>
Reply-To: A mailing list for Enterprise JavaBeans development
Date: Wed, 30 Jun 1999 11:40:54 -0700
>Lisa Retief <[EMAIL PROTECTED]> writes:
: No. Session Beans are not persistent and therefore support neither
: bean-managed or container-managed persistence.
Plus, if they are stateless, what could one want to make persistent ?
I guess a simple properties file or similar would do.
--
Cedric
http://beust.com/cedric
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
