You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brent N Atkinson (JIRA)" <ji...@apache.org> on 2015/04/22 18:58:58 UTC
[jira] [Created] (CONTINUUM-2754) Separate transaction management
from data access code
Brent N Atkinson created CONTINUUM-2754:
-------------------------------------------
Summary: Separate transaction management from data access code
Key: CONTINUUM-2754
URL: https://issues.apache.org/jira/browse/CONTINUUM-2754
Project: Continuum
Issue Type: Task
Reporter: Brent N Atkinson
Currently, the data access code for continuum merges concerns by hard-wiring transaction demarcation into the data access layer. By doing this, it:
* Reduces the utility data access code since it is not possible to have a single transaction span multiple data access calls
* Makes testing slower and more difficult since it is not possible to use transaction rollback to ensure isolated tests
* Increases the coupling between client code and data access, since the transaction semantics need to be known for service code to be written correctly
By pulling transaction management out of the data access code, the service and data access layers can be simpler and all-around more useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)