I don't think that transaction is the right word to use. Transactions
make sure that methods of a beans or beans themselves are part of an
"all for one, or none for all" process. The clich� example is
transferring money from savings to checking. You need to make sure that
adding checking with a specified amount, and deducting from saving by
the same amount happens in the same transaction. If one method completes
and the other doesn't it, someone's going to lose some money.
When you say container or bean managed "persistence" it refers to who is
doing the SQL and Connection programming to put it simply. Container
managed persistence allows you to myBean.setName("Bob") and not worry
about the internals. When you have a legacy DB or something else
strange you might use Bean Manage Persistence.
Session Beans have no persistence although you can use the session bean
to store information into a db. It doesn't remember the information it
has placed in the database. You would only interact the session bean
with the back end when you want to store something that you don't need
to remember.
Hope that helps.
--
Dan Hinojosa
Java & Lotus Notes Consultant
Java Certified Programmer
P.O. Box 4675
Albuquerque, NM 87196-4675
Telephone: (505) 262-0911
Email: [EMAIL PROTECTED]
WWW: http://www.digitalpriest.com
===========================================================================
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".
