Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-630

Versioning operations are not fully transactional

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.9, 1.0, 1.0.1, 1.1
    • None
    • transactions, versioning
    • None

    Description

      Even when DB persistence manager are in use, versioning operations are not fully transactional.
      This is because version storage and workspace uses own db connections and there are in fact 2 local transactions executed. It is always possible that one of them could fail.

      Distributed transactions should be used to make versioning operations fully transactional.

      Attachments

        Issue Links

          incorporates

          Improvement - An improvement or enhancement to an existing feature or task. JCR-1775 Transaction-safe versioning

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JCR-1685 Version node still accessible after transaction rollback

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              ppakulski Przemyslaw Pakulski
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: