[KULRICE-4442] Person service does not handle extension objects properly Created: 17/Aug/10  Updated: 03/Jul/12  Resolved: 03/Jul/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s:
Fix Version/s: 2.0

Type: Bug Fix Priority: Major
Reporter: Jonathan Keller Assignee: Emerson David (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File PersonServiceImpl.java.diff    
Similar issues:
KULRICE-8684ActionRequestValue is not handling missing Person or Group objects
KULRICE-5056Convert DocumentSearch objects and services to new model
KULRICE-11414Extension framework does not work with objects using sequences for primary key
KULRICE-11602Create extension points to override ExpressionEvaluator
KULRICE-7392Another problem with EBOs - PBO.refresh() not handling them properly
KULRICE-4291Person Inquiry not working for external implementations of Identity service. Need to update UiDocumentServiceImpl
KULRICE-5349LookupForm does not serialize properly
KULRICE-3801Fix the way that "empty" KIM objects are handled
KULRICE-4025Direct inquiry does not work properly in some conditions
KULRICE-9119Review design for extension framework in new data layer
Rice Module:
Application Requirement:
KFS, Rice
KAI Review Status: Not Required
KTI Review Status: Not Required


The person service has a problem resolving properties correctly when the person is an attribute on an extension object. KFS patched PersonServiceImpl to give special handling to the "extension" property.

(Previously, it was resolving into strings like businessObjectName.extension.extension.person.principalId)

Comment by Emerson David (Inactive) [ 24/Aug/10 ]

Modified resolvePrinciplNamesToPrincipalIds() to handle extension objects

Comment by Jessica Coltrin (Inactive) [ 03/Jul/12 ]

reopening to set fix version to something other than 1.x-backlog.

Comment by Jessica Coltrin (Inactive) [ 03/Jul/12 ]


Generated at Tue Feb 25 09:38:50 CST 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.