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

Remove the need to inject "cache" into the KSBConfigurer

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-2734Remove the serviceOverrides property from the KSBConfigurer
      KULRICE-11840TermRepositoryService Spring injected needed
      KULRICE-2464Remove AuthorizationService from KSB module
      KULRICE-3787When a custom quartz scheduler is injected into KSBConfigurer, if useQuartzData is true, KSBSchedulerFactoryBean throws errors
      KULRICE-5808Fix cache errors when injecting service containing cache annotations with spring
      KULRICE-5357update our caching solution for rice.
      KULRICE-10169Make TranslationUtility Spring injectible
      KULRICE-12485Adding/Removing a role doesn't take effect even if you clear the kim cache
      KULRICE-11177Need JPA related caching functionality to improve performance and support clustering
      KULRICE-5997Parameter cache keys need to be changed
    • Rice Module:
      KSB

      Description

      The KSBConfigurer currently requires that the "cache" bean be injected into it. This serves to "start" the cache. This was causing timing issues in the unit tests after the Spring context refactoring to make Rice have a single app context.

        Activity

        Hide
        Eric Westfall added a comment -

        Impact here on existing clients is that they need to wire up a RiceCacheExporterFactoryBean instead of a RiceCacheAdminstratorImpl. So where they used to have this:

        <bean id="cache" class="org.kuali.rice.ksb.cache.RiceCacheAdministratorImpl" />

        They would have:

        <bean id="cache" class="org.kuali.rice.ksb.messaging.RiceCacheExporterFactoryBean" />

        Additionally, they no longer need to inject "cache" into the KSBConfigurer.

        Show
        Eric Westfall added a comment - Impact here on existing clients is that they need to wire up a RiceCacheExporterFactoryBean instead of a RiceCacheAdminstratorImpl. So where they used to have this: <bean id="cache" class="org.kuali.rice.ksb.cache.RiceCacheAdministratorImpl" /> They would have: <bean id="cache" class="org.kuali.rice.ksb.messaging.RiceCacheExporterFactoryBean" /> Additionally, they no longer need to inject "cache" into the KSBConfigurer.
        Hide
        Eric Westfall added a comment -

        This has been completed.

        Show
        Eric Westfall added a comment - This has been completed.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1 hour
              1h
              Remaining:
              Remaining Estimate - 1 hour
              1h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Structure Helper Panel