Does anyone have experience with setting a different transaction isolation 
level than the default when using Spring declarative transactions 
(@Transactional)? This seems to be currently unsupported 
(https://jira.springsource.org/browse/SPR-3812) and there seems to be a 
workaround for Hibernate described in this blog: 
http://shahzad-mughal.blogspot.nl/2012/04/spring-jpa-hibernate-support-for-custom.html?showComment=1348666417822#c8785942165526911534

I have a transaction that sets an absolute inventory quantity where the 
quantity is calculated by summing over multiple inventory mutations. This is a 
check-then-act which should be atomic to be correct. If I understand isolation 
levels well, this requires SERIALIZABLE isolation.

Reply via email to