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

Figure out how to handle the potential conflict of having two different documents saving to the same join (i.e. group membership)

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: Not version specific
    • Component/s: Analysis
    • Labels:
      None
    • Similar issues:
      KULRICE-5413figure out how to handle collections being null on model objects when being unmarshalled
      KULRICE-4064Come up with a way to prevent or handle spring bean name conflicts
      KULRICE-5638Figure out how to make caching possible for services in the core module
      KULRICE-7066Issue when two quickfinders on same view have different lookup configuration
      KULRICE-4659Figure out how client apps will publish their KimTypeServices (and other modules' callback service) via SOAP
      KULRICE-11043Person document goes into exception when attempting to deactivate a Person with a single group membership
      KULRICE-97Add paging for large role/group memberships on KIM documents
      KULRICE-351Figure out how to handle CSS Customization from an institutional perspect and buuild this into rice and KNS
      KULRICE-7231Figure out how to fix the EBO issue and replace it
      KULRICE-5018Figure out how to Handle non-database related "Components"
    • Rice Module:
      KIM
    • Application Requirement:
      Rice

      Description

      Because we could have multiple maintenance documents altering the same join record, if we are handling the optimistic locking properly, one maintenance document could technically alter the same join as another.

      This is the case of altering the group membership for a principal from the principal maintenance document and doing the same, but from the group maintenance document.

        Activity

        Hide
        Eric Westfall added a comment -

        This is an old KIM issue, but I'm not sure if a general KNS issue can be extracted from this?

        Show
        Eric Westfall added a comment - This is an old KIM issue, but I'm not sure if a general KNS issue can be extracted from this?
        Hide
        Ailish Byrne added a comment -

        if i'm understanding this correctly, we already have situations like this in kfs. the key is to insert the appropriate maintenance lock representations to prevent the problem from happening up front via the normal mechanisms. e.g. both account delegate global and account delegate modify delegates, so they need to insert locks that block eachother

        Show
        Ailish Byrne added a comment - if i'm understanding this correctly, we already have situations like this in kfs. the key is to insert the appropriate maintenance lock representations to prevent the problem from happening up front via the normal mechanisms. e.g. both account delegate global and account delegate modify delegates, so they need to insert locks that block eachother
        Hide
        Eric Westfall added a comment -

        Great, then I'll close this as won't fix since it was originally encountered as a result of developing the original KIM user interfaces.

        Show
        Eric Westfall added a comment - Great, then I'll close this as won't fix since it was originally encountered as a result of developing the original KIM user interfaces.

          People

          • Assignee:
            Unassigned
            Reporter:
            Aaron Godert (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel