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

Determine the proper way to handle client-side caching and eviction operations


    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-rc1, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-7991Refactor client side state handling
      KULRICE-12301View flag for disabling growls should disable client side growls as well
      KULRICE-10937Determine the best way to handle "refresh reference" and leverage EntityManager.getReference for JPA
      KULRICE-6236EN-548 Document Client-side Dependencies
      KULRICE-3796JPA - Verify that the way we are handling sequences is the proper way to handle them moving forward
      KULRICE-8074Getting client side validation errors when no errors are present
      KULRICE-3947Determine how to handle collections in JPA for existing applications
      KULRICE-9489Determine best way to determine whether KRAD criteria fields treat wildcards and operators as literals
      KULRICE-4891Determine and document the proper way to deal with RuntimeExceptions in Rice
      KULRICE-10179Setting required="true" on field with file indicator does not require upload client side
    • Rice Module:
      Rice Core
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      The spring caching is set up to evict the cache on certain operations if they are configured as such. We annotate on the interfaces, so that means when we load a client-side service, it creates the client-side cache for us. However, i suspect that when someone makes an "update" operation via the service, the eviction gets handled on the client-side (I could be wrong about this, we need to look into it a little bit more). This means the client application making the change would be sending eviction messages to all listening applications on the bus instead of forwarding to the server to have it process evictions. Additionally, this would likely mean that cache eviction happens twice, once when the eviction is processed on the client and once on the server (not good).

      We need to determine if this is actually happening this way in the new Rice caching architecture and figure out a solution if it is.



          • Assignee:
            Eric Westfall
            Eric Westfall
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel