Nice article!

One thing: You show annotation on interface in your example, but actually, the official recommendation is to put the annotation on the class.

Here is an except from the docs at

http://static.springframework.org/spring/docs/2.0.x/reference/transaction.html

"...The Spring team's recommendation is that you only annotate concrete classes with the @Transactional annotation, as opposed to annotating interfaces. You certainly can place the @Transactional annotation on an interface (or an interface method), but this will only work as you would expect it to if you are using interface-based proxies. The fact that annotations are not inherited means that if you are using class-based proxies then the transaction settings will not be recognised by the class-based proxying infrastructure and the object will not be wrapped in a transactional proxy (which would be decidedly bad). So please do take the Spring team's advice and only annotate concrete classes (and the methods of concrete classes) with the @Transactional annotation...."

Great article Willie. The transaction semantics are changing a little in the 2.5.3 branch in a way that you'll have to update your article soon. Please see the release notes under "Transaction Semantics" shaping up on the spring forum: <a href="http://tinyurl.com/2g9mqh">here</a>

@Lucas: :-)

@Tech Per: I moved your comment from the autowiring article to this one because I think that it was meant to go here.

Thanks very much for the nice words and especially for pointing out the problem. I'll update the article accordingly and include an explanation as to what the issue is.

Excellent post. Really enjoyed reading your article.

I was hoping to explore Spring's transaction management and had the Spring doc opened for last few days. You just made all that so so simple! :)

Thanks a lot for your effort.

Awesome article Willie! Very easy to follow. As you mentioned in the article itself, very simple and easy to understand examples.
I'm pretty new to Spring and still learning it. Your article really helped me to easily go through the Transaction management chapter in the Spring book that I'm following :).
Thank you so much for such a nice article.

Really appreciate the feedback. Thanks guys.

Wonderful article... Thanks for it

Really excellent. Thanks for you time and dedication, Willie. It's nice to see that Eclipse (and I'm sure other modern IDEs) will actually offer code completion for the various annotation properties that can be set for @Transactional.

Something curious that I noticed, I had my applicationContext.xml set up with this doctype:

<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">

and when I added your
<beans xmlns="http://www.springframework.org/schema/beans"...
inside that doctype and then tried to deploy I got errors saying that something was wrong with the xmlns declaration. I removed the doctype and it works perfectly. I'm new to Spring so I hope I've done the right thing. (if so, I hope this tip helps someone else).

Thanks Paul. I'm guessing the problems you ran into are related to the fact that that DTD is for Spring 1.2. (If you pull up the DTD in question you can see the reference to Spring 1.2 in the source.) Your namespace declaration on the beans element takes care of validation for you, using XML schemas instead of the older DTD approach.

Very Nice article. Thanks.

Thanks for good article. I have one question : Does spring creates proxy for the classes which are annotated with @Transactional. ?

Is this has something to do with AOP?

Appreciate your reply

Thanks Umesh

Hi Umesh,

Yep, that is exactly how it works: with proxies and AOP. The AOP concept really goes hand-in-hand with the whole dependency injection thing. A lot of times people talk about dependency injection in conjunction with testing, but in my opinion an even more powerful application is being able to add decorations (like transactional behavior) to components and that's exactly what's going on here.

Willie

Thanks Willie, Appreciate your reply.

So it is safe to assume that underlying Transaction have defined Aspect, Pointcut for the @Transaction annotation.

Regards UmeshGohil

Excellent article Umesh!!

Huge thanks Willie. Do you know how to incorporate pre and post interceptors when using annotations for transactions? I'm trying to figure that out.

I found exception when using code above. It said : org.springframework.dao.InvalidDataAccessApiUsageException: Write operations are not allowed in read-only mode (FlushMode.NEVER/MANUAL): Turn your Session into FlushMode.COMMIT/AUTO or remove 'readOnly' marker from transaction definition.

Please your best suggestion to resolve this issue.

Regards, Rendi

Hi Willie,

I am new to Spring and unable to understand the difference between proxy-based vs AOP-based approach. I would really appreciate if you can explain these 2 with sample example and best practices of using this two.

Thanks in advance.

Best Regards - Roy

This is excellent post Willi.

I am new to Spring and unable to understand the difference between proxy-based vs AOP-based approach. I would really appreciate if you can explain these 2 with sample example and best practices of using this two.

Thanks in advance. Khush.

Gucci handbags Gucci Classics Gucci Cruise Gucci Fall Winter Gucci Watches Gucci Gucci jewelry Gucci Jewelry Gucci Wallets links of london links of london Jewellery

he myth of pandora is ancient, appears in several distinct Greek versions, pandora armbandand has been interpreted in many ways. In all literary versions, Neu Eingetroffen however, Pandora Armbänder the myth is a rosetta stone kind of theodicy, addressing the question pop information, web easy get, sports fashion, news-fashionof why there is evil in the world. In the seventh hot-winter century BC, Hesiod, both in his Theogony (briefly, without naming Pandora outright rosetta stone language, rosetta stone spanish, abercrombie and fitch, Abercrombie Fitch