Pluto
  1. Pluto
  2. PLUTO-460

PortletPreferenceDD doesn't descriminate between no (null) values and empty values (new String[0])

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.4
    • Fix Version/s: 1.1.5
    • Component/s: None
    • Labels:
      None

      Description

      PortletPreferenceDD always initialized its values List to "new ArrayList();". This does not account for the portlet.xml to specify a name with no values in the descriptor. This was accounted for in PortletEntityImpl which is only partially related to PortletPreferenceDD and causes problems for other portals using the Pluto container. The fix is to initialize the values List to null.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12565015 ] jira [ 12585930 ]
        Mark Thomas made changes -
        Workflow jira [ 12420363 ] Default workflow, editable Closed status [ 12565015 ]
        Elliot Metsger made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Elliot Metsger made changes -
        Assignee Elliot Metsger [ emetsger ]
        Eric Dalquist made changes -
        Field Original Value New Value
        Attachment pluto_prefsdd.patch [ 12372647 ]
        Eric Dalquist created issue -

          People

          • Assignee:
            Elliot Metsger
            Reporter:
            Eric Dalquist
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development