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

Remove initializing of ComponentSecurity objects for each component

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-8950Finalize on ComponentSecurity
      KULRICE-10107Remove array and map initializing from component constructors
      KULRICE-10106Further reduction of default initialized components
      KULRICE-8954Reduce object creation in component lifecycle
      KULRICE-10021Remove default initialization of tooltip
      KULRICE-7527Remove non-common default bean definitions to reduce initialize view size
      KULRICE-6955When label text is specified on a field but the label component is not initialized, initialize the component in code
      KULRICE-7003Provide a simpler table layout that does not build up field objects for each column
      KULRICE-11779Fix DataDictionaryComponentPublisherServiceImpl to work with data objects
      KULRICE-9422Look into perform initialize add initial component state for elimination
    • Epic Link:
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Sprint:
      2.4.0-m2 Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Creating a component security instance for each component is expensive. This object is not used for most components as well. Instead we can add convenience setters for the component security properties to the component that will initialize the component security instance when needed

        Activity

        Hide
        Daniel Epstein (Inactive) added a comment -

        Jerry Neal, related, is the initialization of additionalPermissionDetails and additionalRoleQualifiers needed in the ComponentSecurity constructor? There are null checks for these already in the view authorizer. It could help cut down on some object initializations.

        Show
        Daniel Epstein (Inactive) added a comment - Jerry Neal , related, is the initialization of additionalPermissionDetails and additionalRoleQualifiers needed in the ComponentSecurity constructor? There are null checks for these already in the view authorizer. It could help cut down on some object initializations.
        Hide
        Jerry Neal (Inactive) added a comment -

        Thanks Dan. I'll create a Jira for removing those.

        Jerry

        Show
        Jerry Neal (Inactive) added a comment - Thanks Dan. I'll create a Jira for removing those. Jerry

          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 - 4 hours Original Estimate - 4 hours
              4h
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 5 hours
              5h

                Agile

                  Structure Helper Panel