Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-8179

Rice KEW considers Maps as 'simple' properties and serializes them and persists them in the database.


    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Rice Module:
    • KRAD Feature Area:
      KEW Integration
    • Application Requirement:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      KC Time and Money documents are persisting a decent amount of data into the KREW_DOC_HDR_CNTNT_T table because the 'document' contains a number of 'simple' hashmaps.

      This happens in PropertySerializerTrie.addSerializablePropertyName when the propertyName 'document' is passed in. Which always happens as the document should be persisted. It then sets that object to serialize all simple properties. In PropertySerializabilityEvaluatorBase.determinePropertyType it determine primitive objects to be anything that is not a BO and a Collection. As Maps are neither, all maps on our documents are persisted in the Doc Content XML. This seems to be an oversight as collections are not included and should be reviewed.

      Should maps be a separate property type in determinePropertyType or is there a better way to use the workflowProperties to control which properties on the document are serialized and thereby not serialize unnecessary maps on KC documents. KC currently has a few documents that have multiple maps in them and serializing these documents leads to a large amount of data being persisted in the database.


          Issue Links


            Error rendering 'com.atlassian.jira.jira-view-issue-plugin:activitymodule'. Please contact your JIRA administrators.


              • Assignee:
                sonam Sona Sona (Inactive)
                gathreya Gayathri Athreya
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: