I'm referring this - 5.4.3 Transaction Attributes Table Bean-managed (page 55)
from Enterprise Java Beans 3.pdf by Frits.
I have understood if a client invokes Bean Managed Transaction method, the client's transaction is always suspended. I don't understand two things in this topic.
1. What is the difference between transaction associated with instance and with the method?
2. How and why transaction currently associated with the instance is only applicable for a Stateful SB?
May be I can remember if somebody hints me.
Cheers,
IndoKnight
Transaction Attributes Table Bean-Managed
Moderator: admin
-
- Posts: 9
- Joined: Thu Feb 27, 2014 11:47 am
- Contact:
-
- Site Admin
- Posts: 10102
- Joined: Fri Sep 10, 2010 9:26 pm
- Contact:
Re: Transaction Attributes Table Bean-Managed
A stateful bean instance is locked to a particular client and so it is possible to span a transaction accross multiple method calls. Therefore, such a transaction is associated with the instance.
In case of other beans, a client's call can be routed to any instance of a bean. Therefore transaction cannot span more than a method. Hence, the transaction has to be associated with a method.
In case of other beans, a client's call can be routed to any instance of a bean. Therefore transaction cannot span more than a method. Hence, the transaction has to be associated with a method.
If you like our products and services, please help us by posting your review here.
-
- Posts: 9
- Joined: Thu Feb 27, 2014 11:47 am
- Contact:
Re: Transaction Attributes Table Bean-Managed
Yes, that makes sense.
Thank you.
Cheers,
IndoKnight
Thank you.
Cheers,
IndoKnight
Who is online
Users browsing this forum: No registered users and 1 guest