Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-9553

Implement concept of a "Conversation" managed by the framework, to support extended persistence contexts for lazy loading

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development, JPA, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-3890Determine how best to handle persistence, attached/detached, and lazy loading for the BusinessObjectService in the context of KNS
      KULRICE-9118Implement better support for a concept similar to ExternalizableBusinessObjects in the new krad-data framework
      KULRICE-9320Determine out-of-the-box configuration for EclipseLink dynamic weaving support for lazy loading
      KULRICE-6841UIF Framework - Introduce the concept of data element attributes
      KULRICE-9220Implement facility for preventing legacy persistence framework use at runtime
      KULRICE-5398Implement proper thread-safe lazy initialization for WorkflowDocumentFactory
      KULRICE-6014JPA Conversion Guide
      KULRICE-10257Implement support for inquiry in conversion scripts
      KULRICE-383Finish implementing lazy loading of DD files; fix up unit tests
      KULRICE-7243Add support for adding term specs to a Context
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Persistence Framework
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      In order to better support lazy loading of entities which are modified and read over multiple request-response cycles by the framework, we really need to implement the concept of a conversation which is started at the beginning of a maintenance document creation or edit, and cleaned up after the user is done working with the document.

      We need to do some analysis first on what the design for this will look like. Additionally, this will only be necessary for JPA implementations which don't allow lazy loading after the original entity manager is closed (i.e. Hibernate) so this could be an optional feature if we are just doing EclipseLink support.

        Activity

        Hide
        Claus Niesen added a comment -

        Need to determine first if we can support hibernate.

        Show
        Claus Niesen added a comment - Need to determine first if we can support hibernate.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 1 week
              1w
              Remaining:
              Remaining Estimate - 1 week
              1w
              Logged:
              Time Spent - Not Specified
              Not Specified

                Structure Helper Panel