This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes CMT in JAVAEE5.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "CMT in JAVAEE5.0 " Watch "CMT in JAVAEE5.0 " New topic
Author

CMT in JAVAEE5.0

walter wang
Ranch Hand

Joined: Jun 02, 2001
Posts: 150
Dear all,

I encounter a roll back problem for my transactions in my stateless session ( implemented under EJB3.0 standard ).

According to below quoted sentence from JAVAEE5.0 Tutorial.

If I didnot explicitly mark transaction for my stateless session's methods
then all those methods are automatically Contain transactin managed , is it correct?
but it seems .the method doesnot roll back successfully when a exception happened inside it. I used JBoss4.0 + Stateless SessinBean (no explicit transacation demarcation used ).

Any hints? Is it a transacatin problem from JBoss or my misunderstanding to
CMT for Stateless Session Bean?

Thanks in advances



Container-Managed Transactions

In an enterprise bean with container-managed transaction demarcation, the EJB container sets the boundaries of the transactions. You can use container-managed transactions with any type of enterprise bean: session, or message-driven. Container-managed transactions simplify development because the enterprise bean code does not explicitly mark the transaction's boundaries. The code does not include statements that begin and end the transaction.

By default if no transaction demarcation is specified enterprise beans use container-managed transaction demarcation.


public class Walter { public boolean is_Working_Now (boolean is_boss_Coming) { return is_boss_Coming; }
walter wang
Ranch Hand

Joined: Jun 02, 2001
Posts: 150
I found the reason
cos I should only throw SystemException, then CMT can roll back correctly
SystemException is the sub class Exception of EJBException
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: CMT in JAVAEE5.0
 
Similar Threads
Passed Part One with 87%
My Study Notes
Reg SessionSynchronization Interface
Transaction handling in Session Bean
ejbCreate -permitted and prohibited operations -