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

Investigate whether we should publish methods on services to flush caches


    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: 2.0.0-b1
    • Fix Version/s: 2.0.0-b6, 2.0
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-5942See if we can improve our cache flushing with new Spring cache annotations
      KULRICE-2812Review services we are publishing as SOAP services, ensure we have everything we need published
      KULRICE-12457KRMS error and cache flush messages not appearing right
      KULRICE-6533Rename cache service endpoints to "cache admin service" since that's what we renamed the actual service interface to
      KULRICE-6759Add manual flush method on the IdentityArchiveService.
      KULRICE-2418Implement cache aging and flushing on PersonServiceImpl
      KULRICE-7258Implement caching on ExtensionRepositoryService
      KULRICE-5209Add servicePath to all of our Kuali Rice services that we are publishing
      KULRICE-13189modify KRMS' published apis so that update methods return the updated object
      KULRICE-8327Implement caching for Message Service
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      Currently cache's are flushed on update and create methods, but should we have a method that flushes the cache with a call? It seems possible that some institutions would have a batch job that doesn't use the service for crud (db updates?), and it seems like in that instance there should be an easier way for them to clear the cache.


        No work has yet been logged on this issue.


          • Assignee:
            Jeremy Hanson
            Jeremy Hanson
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel