Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-9422

Look into perform initialize add initial component state for elimination

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-10106Further reduction of default initialized components
      KULRICE-10105Remove initializing of ComponentSecurity objects for each component
      KULRICE-11572Maintenance Pages not routing out of initiated
      KULRICE-11573Maintenance Pages not routing out of initiated
      KULRICE-6955When label text is specified on a field but the label component is not initialized, initialize the component in code
      KULRICE-9218Components for pages not displayed not getting ids causes state issues
      KULRICE-10349The expanded/collapsed state does not persist on refreshed INITIATED documents
      KULRICE-13786Create Initial performance CI job for Doc Search
      KULRICE-7527Remove non-common default bean definitions to reduce initialize view size
      KULRICE-10107Remove array and map initializing from component constructors
    • Epic Link:
    • Rice Module:
      KRAD
    • Sprint:
      2.4.0-m3 KRAD Sprint 1, 2.4.0-m3 KRAD UXI Sprint 3, 2.4.0-m3 KRAD UXI Sprint 4, 2.4.0-m4 KRAD UXI Sprint 2, 2.4.0-m4 KRAD UXI Sprint 3
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Adding the initial state of a component to the index (with the cloning) is a performance issue. Determine if this can be avoided or optimized

      Requiring ids on beans will eliminate the need to store initial state

      Also, for cases where components are created in code, look into providing an application level cache

      Another possibility is to require implementation of an interface 'RefreshableComponent' to rebuild the initial state

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          removing m3 fix version since these aren't assigned and will not be done by Monday's m3 release.

          Show
          Jessica Coltrin (Inactive) added a comment - removing m3 fix version since these aren't assigned and will not be done by Monday's m3 release.
          Hide
          Mark Fyffe (Inactive) added a comment -

          Committed fix in-lifecycle rendering following changes related to this issue.

          testSanity(org.kuali.rice.krad.uif.lifecycle.ViewLifecycleTest)  Time elapsed: 0.125 sec  <<< FAILURE!
          org.junit.ComparisonFailure: expected:<[R]> but was:<[F]>
                  at org.junit.Assert.assertEquals(Assert.java:115)
                  at org.junit.Assert.assertEquals(Assert.java:144)
                  at org.kuali.rice.krad.uif.lifecycle.ViewLifecycleTest.testSanity(ViewLifecycleTest.java:106)
          

          Render phase needs to be initialized with the number of child render phases, which should match the number of successor finalize phases; the render phase uses the finalize phase tree as the basis for bottom-up tree traversal.

          Show
          Mark Fyffe (Inactive) added a comment - Committed fix in-lifecycle rendering following changes related to this issue. testSanity(org.kuali.rice.krad.uif.lifecycle.ViewLifecycleTest) Time elapsed: 0.125 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[R]> but was:<[F]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.kuali.rice.krad.uif.lifecycle.ViewLifecycleTest.testSanity(ViewLifecycleTest.java:106) Render phase needs to be initialized with the number of child render phases, which should match the number of successor finalize phases; the render phase uses the finalize phase tree as the basis for bottom-up tree traversal.
          Hide
          Mark Fyffe (Inactive) added a comment -

          Merged latest updates from trunk to performance branch. Working now on CollectionGroup controller methods conversion.

          Show
          Mark Fyffe (Inactive) added a comment - Merged latest updates from trunk to performance branch. Working now on CollectionGroup controller methods conversion.
          Hide
          Jerry Neal (Inactive) added a comment -

          Resolving, will create smaller issue for remaining work

          Show
          Jerry Neal (Inactive) added a comment - Resolving, will create smaller issue for remaining work

            People

            • Assignee:
              Jerry Neal (Inactive)
              Reporter:
              Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 days Original Estimate - 3 days
                3d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 2 days, 6 hours
                1w 2d 6h

                  Agile

                    Structure Helper Panel