Details
-
Type:
Bug Fix
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0.1.1, 1.0.2
-
Fix Version/s: 2.0
-
Component/s: Development, Version Compatibility
-
Labels:None
-
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.
Attachments
Issue Links
- is related to
-
-
- Open
-
-
KULRICE-4641 Fix Remote Mode in KIM
-
- Open
-
- Trackbacks
-
![[Confluence: Cynergy]](/images/icons/generic_link_16.png "[Confluence: Cynergy]")
Analysis of Cynergy 2.0.x Customizations
(Still under construction) Customization Description Rice 1.0.3 Impact Customization JIRA Resolution JIRA Outcome KIMServiceLocator, KEWServiceLocator, and SpringResourceLoader Customization These classes were customized as part of a patch Chad H....
Activity
Specifically, see KULRICE-4303 for details on other KIM remote mode problems.
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.
Closing since these items are now in the release notes.