CdmTransactions » History » Version 4
Andreas Kohlbecker, 04/04/2013 11:54 AM
1 | 1 | Andreas Kohlbecker | |
---|---|---|---|
2 | 4 | Andreas Kohlbecker | # Transactions in the CDM Library |
3 | |||
4 | |||
5 | _Information on transactions in the cdm. How transactions are configured and why they are configured in a specific way. Furthermore in future this page can contain also information on transaction boundaries and the like._ |
||
6 | 2 | Andreas Kohlbecker | |
7 | |||
8 | |||
9 | ## The default propagation strategy for service classes is `Propagation.SUPPORTS` |
||
10 | |||
11 | |||
12 | With r8688 `Propagation.SUPPORTS` as been set as default propagation strategy for all service classes: |
||
13 | |||
14 | |||
15 | ~~~ |
||
16 | @Transactional(readOnly = true, propagation = Propagation.SUPPORTS) |
||
17 | class ... |
||
18 | ~~~ |
||
19 | |||
20 | This has been only introduced to prevent early commit in Spring Web-flow. |
||
21 | |||
22 | |||
23 | In Forums and blocks the recommendation to set the propagation strategy to Propagation.SUPPORTS, this should increase the performance: |
||
24 | |||
25 | |||
26 | * http://stackoverflow.com/questions/10750445/how-to-apply-transactions-best-practice-for-read-operations-in-spring-mvc-using |
||
27 | |||
28 | * http://forum.springsource.org/showthread.php?61190-Propagation-Support-readOnly-true-vs-no-transactin-at-all |
||
29 | |||
30 | |||
31 | We tested the effect of setting propagation strategy to `Propagation.SUPPORTS` and could not find a significant difference. |
||
32 | |||
33 | see attachment:Propagation.SUPPORTS-vs-Propagation.REQUIRED.ods |