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

ReferenceLinker.linkObjectsWithCircularReferenceCheck in krad-data needs to handle formatting when setting the property value

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Development, JPA, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-10904Ability to format property values in code
      KULRICE-6845Problems with UifBeanFactoryPostProcessor expression handling that is causing bean property overrides (such as fieldInquiry.render) to not work
      KULRICE-10305Lookup: Set default values on "clear values"
      KULRICE-8295Null handling in DocumentSearchCriteriaBo.groovy needs work
      KULRICE-9240UifBooleanEditor Property Editor formatted string values
      KULRICE-5377Develop utility class that will apply formatting using the spring property editors
      KULRICE-8425Problems with UifBeanFactoryPostProcessor expression handling for nested properties and lists prevent bean property overrides (such as fieldInquiry.render) from working
      KULRICE-6853Currency Format exception on Null values
      KULRICE-11780Parameter needed in AttributeReferenceDummy-activeIndicator to set default value
      KULRICE-10454Improve handling of the binding errors
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Persistence Framework
    • Sprint:
      Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      In order to remove the OJB dependencies from krad-data module, I had to modify this method so that it no longer used ObjectUtils.setObjectProperty and instead just set the property using the Accessor api. However, this ObjectUtils method was also attempting to "format" and/or convert the incoming property value if it was a String or the types were different. It did this by looking for a formatter in the DD and applying that.

      At the time I wasn't sure the best way to replicate that, so once we determine what the replacement is for ObjectUtils.setObjectProperty we need to go back to this method on ReferenceLinker and fix it (look for the lines with the comments referencing this jira).

        Activity

        Hide
        Eric Westfall added a comment -

        It was decided in the checkpoint meeting today that we can just use plain old setPropertyValue because in the context of the ReferenceLinker there is no need to format the values. So I'm closing this one.

        Show
        Eric Westfall added a comment - It was decided in the checkpoint meeting today that we can just use plain old setPropertyValue because in the context of the ReferenceLinker there is no need to format the values. So I'm closing this one.

          People

          • Assignee:
            Eric Westfall
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1 hour
              1h
              Remaining:
              Remaining Estimate - 1 hour
              1h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Agile

                  Structure Helper Panel