[KULRICE-4140] KimTypeInfoService cannot be accessed by "remote" KIM clients directly Created: 03/May/10  Updated: 23/Feb/12  Resolved: 28/Jun/11

Status: Closed
Project: Kuali Rice Development
Component/s: Development, Version Compatibility
Affects Version/s: 1.0.1.1, 1.0.2
Fix Version/s: 2.0

Type: Bug Fix Priority: Major
Reporter: Chad Hagstrom Assignee: Travis Schneeberger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day

Issue Links:
Relate
is related to KULRICE-4303 Document initiator check fails when K... Open
is related to KULRICE-4641 Fix Remote Mode in KIM Open
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.



 Comments   
Comment by Eric Westfall [ 29/Aug/10 ]

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.

Comment by Eric Westfall [ 29/Aug/10 ]

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

Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]

Closing since these items are now in the release notes.

Generated at Tue Mar 02 17:56:01 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.