[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
Similar issues:
KULRICE-8798Look into multithreading during the view lifecycle
KULRICE-13147Inefficiencies in view lifecycle and rendering
KULRICE-8797Reduce object creation in view lifecycle
KULRICE-10810Look into transaction view lifecycle
KULRICE-10547Component lifecycle processing task and execution context
KULRICE-11062Do POC on changing lifecycle to use reflection
KULRICE-8468Performance: Collect templates through view lifecycle and include once in view rendering
KULRICE-10438Analysis for delaying lifecycle row details component before it is needed
KULRICE-12548Rich messages not getting processed for image cutline text
KULRICE-7009Profile the view process (complete request/response) for bottlenecks
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 Jan 26 09:00:11 CST 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.