castor
  1. castor
  2. CASTOR-3105

Seperate cache handling which are both handled by TypeInfo and LockEngine

    Details

    • Type: Improvement Improvement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.3.2
    • Fix Version/s: 1.3.3rc1
    • Component/s: JDO
    • Labels:
      None
    • Number of attachments :
      0

      Description

      TypeInfo and LockEngine all deals with some cache, this issue will eperate cache handling which are both handled by TypeInfo and LockEngine

        Activity

        Hide
        Ralf Joachim added a comment -

        After quite some refactoring around LockEngine, TypeInfo and ObjectLock it turns out that seperation of cache and lock handling at TypeInfo is not possible. I therefore resolve this as won't fix,

        Show
        Ralf Joachim added a comment - After quite some refactoring around LockEngine, TypeInfo and ObjectLock it turns out that seperation of cache and lock handling at TypeInfo is not possible. I therefore resolve this as won't fix,

          People

          • Assignee:
            Wensheng Dou
            Reporter:
            Wensheng Dou
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: