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

Add a "THIN" client run mode to KEW, KIM, and KSB modules

        Details

        • Type: Improvement Improvement
        • Status: Closed Closed
        • Priority: Critical Critical
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 2.0.0-rc2, 2.0
        • Component/s: Configuration
        • Security Level: Public (Public: Anyone can view)
        • Labels:
          None
        • Similar issues:
          KULRICE-7549KSBConfigurer attempts to run MessageFetcher when KSB run mode is set to "THIN"
          KULRICE-4902Rice Thin Client Refactor
          KULRICE-3784KEW Thin Client integration does not work properly
          KULRICE-3778KEW Thin Client mode appears to load the entire KEWSpringBeans.xml file, resulting in encryption.key being required to be specified
          KULRICE-7093KSB Module UI is not available on client applications
          KULRICE-3721The "remote" run mode for KIM (and other Rice modules?) does not allow proper consumption of services from the bus
          KULRICE-2983Update thin client integration model so that it provides for proper connection to KIM services
          KULRICE-3950Allow KNS-enabled client applications to run KEW in "remote" mode.
          KULRICE-6360Remove RunMode.THIN and other traces of legacy "THIN" mode as it is no longer needed
          KULRICE-9588Correct KEW documentation on implementing a thin client
        • Rice Module:
          KSB, KEW, KIM
        • KAI Review Status:
          Not Required
        • KTI Review Status:
          Not Required

          Description

          This run mode should be the same as REMOTE with the exception that it shouldn't publish client-side cache admin services.

          I was realizing that we probably need this as I was doing the rice-remote-test-client application to help people who have used the KEW thin client in the past to migrate over more easily. KEW (at the moment) doesn't have any client-side caching on it's services that we would really need to do. KIM does, but in 1.0.x we basically set up that client side cache with reasonable defaults for timeouts since the client would never get any callbacks from the server. So we can probably do something similar here with a custom ehcache configuration file for KIM "thin" mode.

          In KSB, we should just have thin client mode configured to not load messaging and the like.

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            Eric Westfall added a comment -

            Thin run mode has now been implemented for KSB, KEW, and KIM. Tested it out using the rice-remote-test-client

            Show
            Eric Westfall added a comment - Thin run mode has now been implemented for KSB, KEW, and KIM. Tested it out using the rice-remote-test-client
            Hide
            Permalink
            Jessica Coltrin (Inactive) added a comment -

            Closing since these items are now in the release notes.

            Show
            Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel