[KULRICE-7220] Look into replacing component update process with full view lifecycle Created: 29/Apr/12  Updated: 03/Apr/13  Resolved: 30/Apr/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.2.0-m1, 2.2
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Critical
Reporter: Jerry Neal (Inactive) Assignee: Jerry Neal (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
cloned from KULRICE-7208 Template Closed
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


Due to problems with the component update (parent setting of properties) look into performing the full view lifecycle (but only render the component).

In addition, combine page updating with component update so there are not two distinct sets of logic.

Comment by Jerry Neal (Inactive) [ 30/Apr/12 ]

Updating to full view lifecycle causes very large losses in performance times

Generated at Sun Apr 11 10:48:49 CDT 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.