Your
architect is right, handling transactions in the database has much better
performance than compared to using J2EE transactions.
There
are many scenarios where J2EE transaction is used.
In our
project we have used UserTransaction, since the data which the user is entering
is critical, and the logic for inserting the data is written in the Session
beans, and the data is inserted into database via Entity beans i.e. CMP. The
data as has to be ATOMIC, having transactions in the Middleware is more
suitable.
If
your database is fixed.. its not gonna change, then its much better performance
wise to put the logic and transaction handling in the
database.
vikram.
=========================================================================== 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".-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]On Behalf Of Ranjit Gopalan
Sent: Saturday, October 11, 2003 10:20 PM
To: [EMAIL PROTECTED]
Subject: Transactions when are they used
The architect for one of our project opted for database transactions instead of EJB transactions. The reasons given for this are
1. Performance
2. Single datasource.So what is the design requirment to start using middle ware transactions other than multiple datasources.
A follow up of the question
Are really transactions used in J2EE project?. I found not a lot of projects have used EJB transactions when i did a g search and had discussion with my friends. Am i correct to assume this.
Thanks
Ranjit
=========================================================================== 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".
