Spring Transaction Management: Finally Understandable | by

[@maasmans]

All your material is so easy to follow and comprehensible. Thanks to you I finally feel like a I have the ability to actually understand Spring. Thanks so much.

[@AyratVideo]

Nice smile! So look as Alex ) And great stuff! Best explanation ever! Thanks so much.

[@pawenowinski2072]

Great job ! FInally get it ! Thanks : )

[@iSkvort]

One note it uses CGLib only if you have classes. If your beans are implements interface then spring creates a dynamic proxy for bean which is much faster than cglib.

[@alexsav7427]

Thanks for the explanation. I finally understood.

[@rahulshivhare5682]

What's the Difference in manual and spring initiated propagation ?

[@amargupta1728]

Hi, Nice I but just want to know that why proxy objects will be created for calling transactional?

[@GuitarreroDaniel]

I think is a lot easier to set up your DataSource in application.properties than inside a class. Just makes everything look much cleaner.

[@chukwuebukag.anazodo6915]

Hi Marco, Does Transactional annotation also handle race condition problems

[@MarcoBehler]

Hi Chukwuebuka, what kind of race condition problems are you thinking about? Transactional really just opens a databaser transaction, that's it. So it all depends on your isolation levels.

[@chukwuebukag.anazodo6915]

@@MarcoBehler Does is lock a row or entire table until the transaction is committed?

[@josephmbimbi]

the dislike / like ratio is unfair i think. That is a great video

[@neetigupta5468]

nice explanation 👌 thanks

[@LvyZ666]

Creepy smile at the beginning. Good stuff nonetheless!

[@MarcoBehler]

Takes a while to get to an authentic smile in front of a camera :D

[@seyedalihejazi4926]

but lovable

[@OzoneGrif]

When you write the transactionManager, shouldn't you inject the database bean, instead of calling database() directly? It feels like you instance two database driver here.

[@MarcoBehler]

That's a good question! The answer is that spring does some magic here, i.e. whenever it creates your configuration class, it actually creates a cglib proxy of that class which basically "caches" every method invocation. That's why there won't be multiple instances of the data source, only one, even if you call the method directly, instead of injecting

[@mkyrychenko]

@@MarcoBehler but you will be not able to mock the database bean and inject it as parameter, if you need this... Better approach IMHO is to inject in order to have controlled and easy mockable call flow

[@zakb.7108]

I was actually asking myself the same question when finding those method calls on the books, seems like spring "proxy" calls and you'll get the same instance every time.

[@Dev_pig]

Oh, cglib is used by spring. Thank u for your great tutorial :)

[@MarcoBehler]

There you go :) Glad you like it

[@Chesteryoshka]

only if it can't use proxy based on interfaces

[@gudurusivareddy6363]

awesome

[@rrr83]

Thanks for the explanation! You should put your own udemy course to get more audience!