Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: Configuration, Development
    • Labels:
      None
    • Similar issues:
      KULRICE-5357update our caching solution for rice.
      KULRICE-11177Need JPA related caching functionality to improve performance and support clustering
      KULRICE-3222Ensure that ParameterServerService can be remoted and improve caching in ParameterServiceProxyImpl
      KULRICE-8327Implement caching for Message Service
      KULRICE-1512improve configurability of drop-down value caching
      KULRICE-5100StyleServiceImpl.getStyle should perform caching of styles
      KULRICE-5997Parameter cache keys need to be changed
      KULRICE-4410For doc search, don't call new initiator caching code if there is no search results
      KULRICE-8955MessageServiceImpl getDefaultLocaleCode Caching
      KULRICE-5942See if we can improve our cache flushing with new Spring cache annotations
    • Application Requirement:
      KFS

      Issue Links

        Activity

        Hide
        Aaron Hamid (Inactive) added a comment -

        We might want to investigate Terra Cotta. http://www.terracotta.org/

        One question is its license, which is a variant of MPL:

        http://www.terracotta.org/confluence/display/wiki/FAQ#FAQ-LicensingFAQ

        Show
        Aaron Hamid (Inactive) added a comment - We might want to investigate Terra Cotta. http://www.terracotta.org/ One question is its license, which is a variant of MPL: http://www.terracotta.org/confluence/display/wiki/FAQ#FAQ-LicensingFAQ
        Hide
        Ailish Byrne added a comment -

        sorry, i just want to make sure i'm understanding this correctly. when we move to jpa, we will have a replacement for the current ojb persistence broker caching we now do right, even though it will be a vendor specific implementation, our projects will be set up to use it?

        Show
        Ailish Byrne added a comment - sorry, i just want to make sure i'm understanding this correctly. when we move to jpa, we will have a replacement for the current ojb persistence broker caching we now do right, even though it will be a vendor specific implementation, our projects will be set up to use it?
        Hide
        Nate Johnson (Inactive) added a comment -

        If you are referring to the per broker cache, then yes, we will have that out of the box and that is not vendor specific. It's part of the API and is called a persistence context.

        I guess the vendor specific caching I was referring to would be a 2nd level cache... OJB sorta supports that concept, though I've never seen it work well in a distributed environment.

        Show
        Nate Johnson (Inactive) added a comment - If you are referring to the per broker cache, then yes, we will have that out of the box and that is not vendor specific. It's part of the API and is called a persistence context. I guess the vendor specific caching I was referring to would be a 2nd level cache... OJB sorta supports that concept, though I've never seen it work well in a distributed environment.
        Hide
        Ailish Byrne added a comment -

        cool - thanks for the clarification!

        Show
        Ailish Byrne added a comment - cool - thanks for the clarification!
        Hide
        Jessica Coltrin (Inactive) added a comment -

        Caching was redone in Rice 2.0 and should address the items in this old Jira.

        Show
        Jessica Coltrin (Inactive) added a comment - Caching was redone in Rice 2.0 and should address the items in this old Jira.

          People

          • Assignee:
            Unassigned
            Reporter:
            Dan Lemus (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel