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

KimTypeInfoService cannot be accessed by "remote" KIM clients directly

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.1.1, 1.0.2
    • Fix Version/s: 2.0
    • Labels:
      None
    • Similar issues:
      KULRICE-5212Implement RuleService, RuleAttributeService, and related such that they are accessed remotely via SOAP instead of via direct database calls to the rule tables
      KULRICE-3455Possible issues with remoting of KIM Type Services and attributes
      KULRICE-4816Implement interaction with the service registry so that it goes over remote connection instead of direct database access
      KULRICE-4666Evaluate "remote" KIM services
      KULRICE-4668Evaluate remote KIM services: implementation
      KULRICE-3950Allow KNS-enabled client applications to run KEW in "remote" mode.
      KULRICE-4667Evaluate remote KIM services: analysis & decision
      KULRICE-9221Invalid bean name "matchAllTxInterceptor" for KIM Remote mode
      KULRICE-2746No remote services available for client access when attempting to lookup '{KFS}KCB-MessagingService'
      KULRICE-2983Update thin client integration model so that it provides for proper connection to KIM services
    • Rice Module:
      KIM

      Description

      Cornell's KFS implementation has been experiencing problems related to accessing the KimTypeInfoService when running KIM in "remote" mode, where there are some situations in which the KFS application is attempting to retrieve the KimTypeInfoService itself even though KIMImplementationSpringBeans.xml does not expose it on the bus. I believe the "kimTypeInfoService" should be getting exposed on the bus by local/standalone Rice applications, since it returns KimTypeInfos instead of KimTypeImpls and since various parts of KFS (such as the lookupable helper service for OrgReviewRole) need access to it.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          As it stands there are a few major issues with KIM in remote mode when used in conjunction with the KNS (and possibly elsewhere). To that end, I'm going to defer this one and we can work on this as part of the work to improve KIM remote support in 1.1. Let me know if anyone thinks this will be a problem.

          Show
          Eric Westfall added a comment - As it stands there are a few major issues with KIM in remote mode when used in conjunction with the KNS (and possibly elsewhere). To that end, I'm going to defer this one and we can work on this as part of the work to improve KIM remote support in 1.1. Let me know if anyone thinks this will be a problem.
          Hide
          Eric Westfall added a comment -

          Specifically, see KULRICE-4303 for details on other KIM remote mode problems.

          Show
          Eric Westfall added a comment - Specifically, see KULRICE-4303 for details on other KIM remote mode problems.
          Hide
          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:
              Travis Schneeberger
              Reporter:
              Chad Hagstrom
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel