Keep in mind though that if you mix data access code in the same transaction, that uncommitted data may be maintained in different locations.
So, if your CMP is updated and then the BMP through a stored proc (within the same transaction) for example expects to see that uncommitted data (possible if not a Serializable isolation level), you will have a problem because most containers do not push uncommited data from CMP till commit time for performence.
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
Joined: Mar 27, 2004
So, if separate my app in use cases and implement the persistence layer of those use cases in different techonologies, i'm allright?
Clearing... Suppose i have 3 big use cases in my system, if i implement - use case 1 with CMPs - use case 2 with hibernate - use case 3 with jdo and theese use cases don't interfer in each other, i don't need to worry about this kinda of transaction stuff. Am i right?
Joined: Aug 10, 2001
So long as the transactions in each use case stay out of each others way (don't update the same tables) then yes. If they do, then all of the problems that Roland discusses must be addressed.