[Springframework-developer] Transactions / AOP / Hibernate

[petra s. <ca...@ho...>]

Hi

I have a question to the transaction handling with Springframework,
in details, applying Declarative Transaction Demarcation (as outlined
in the "Data Access with the Spring Framework" on Hibernates site).

In advance, sorry for my little knowledge on AOP which may be the
main reason for my question here... ;

Well, as I understood, you can declare an "Interceptor" which inserts/
"weaves in" transaction management code into the appropriate class
methods. I think this happens when entering and exiting the methods
or am I wrong?

In my little application, I have (as suggested by Dmitry in an earlier
posting) created DAO objects, which do not know anything about trans-
actions and soley perform "basic" database work, and business
objects, or "management beans" which use these DAO objects and provide
the final interface for persisting methods to the user.

In my case I have now business/management object which make use of
more than only one DAO (is this ok?). I would like to things like

BusinessObject {
   a_Method {
		(Transactions start by Interceptor??)

		DAO_A.do_something;      ---> requires transactions

		DAO_B.do_something_else; ---> must not be transaction oriented

		(Transaction commit by Interceptor??)
   }
}

Can I somehow get control of the actual transaction functionality?
What possiblities do I have? Are rollbacks automatically performed if
something goes wrong?

This AOP stuff does for me some "magic" stuff, I just can't grasp somehow... 
:-)


Thanks for any Springframework-brush ups! ;-)

_________________________________________________________________
MSN Hotmail  -  Absolut kostenfrei! Der weltweit grösste E-Mail-Anbieter im 
Netz:  http://www.msn.ch/hotmail