Timeline for Simple and Composite transactional services: Question about separation of concerns and transactions
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2016 at 19:47 | comment | added | Borjab | Service composition will lead to nested transactions only if you create the parent service with the Transactional annotation so it is easy to avoid it.,. if you do not need the transactionality. | |
| Dec 1, 2014 at 13:26 | comment | added | cbmeeks | Those are good points. I've actually gone with a "Facade Pattern" somewhat which is what I talking about above. Still seems a little unnatural for me. | |
| Nov 28, 2014 at 11:37 | history | answered | alekseevi15 | CC BY-SA 3.0 |