@Transactional("transactionManager") and error handling [SPR-6810]

[spring-projects-issues]

Michael Isvy opened SPR-6810 and commented

Starting from Spring 3.0 I now can declare the transactionManager inside my @Transactional annotation as follows:

@Transactional("transactionManager")
public void updateClient(Client client) {
...
}

However, if I try that with a transactionManager that does not exist (such as @Transactional("foo")), there is no error message. I believe it just ignores the annotation.
It would be much safer if I had an error at startup saying that the transactionManager does not exist.

---

Affects: 3.0 GA

Referenced from: commits c5c38c6

[spring-projects-issues]

Juergen Hoeller commented

It's unfortunately not quite trivial to do this at startup, since we're generally only evaluating @Transactional when actually configured and actually invoked. For example, you won't get an error when using @Transactional with no tx:annotation-driven setup at all either...

I guess STS could check whether @Transactional qualifiers have a matching PlatformTransactionManager bean in the config set. That should be easy enough to do.

In any case, the framework will throw an exception now if no matching PlatformTransactionManager bean has been found for a given @Transactional qualifier value.

Juergen