Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-beta1
    • Component/s: Runtime
    • Labels:
      None

      Description

      Currently, the transaction management cannot be changed by the user on a general basis (i.e. it is possible to handle transactions totally outside Torque by passing a database connection into the methods, but there is no place to plug in an own transaction management into torque).This makes using external transaction management systems (e.g. Spring's @Transactional annotation) difficult.
      To achieve pluggability, the Transaction class should pass all method calls to an implementation class which can be exchanged by an entry in the Torque runtime configuration.

      There are no Sub-Tasks for this issue.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Thomas Fox
            Reporter:
            Thomas Fox
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development