You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2008/01/11 02:20:34 UTC

[jira] Resolved: (PLUTO-460) PortletPreferenceDD doesn't descriminate between no (null) values and empty values (new String[0])

     [ https://issues.apache.org/jira/browse/PLUTO-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger resolved PLUTO-460.
----------------------------------

    Resolution: Fixed

Committed to 1.1.x r611004.

> PortletPreferenceDD doesn't descriminate between no (null) values and empty values (new String[0])
> --------------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-460
>                 URL: https://issues.apache.org/jira/browse/PLUTO-460
>             Project: Pluto
>          Issue Type: Bug
>    Affects Versions: 1.1.4
>            Reporter: Eric Dalquist
>            Assignee: Elliot Metsger
>             Fix For: 1.1.5
>
>         Attachments: pluto_prefsdd.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.