[jira] [Closed] (PLUTO-698) TCK: Contesting V2AddlFilterTests which assume getInitParameterNames returns parameters in a particular order

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

Neil Griffin closed PLUTO-698.
------------------------------
       Resolution: Fixed
         Assignee: Neil Griffin  (was: Scott Nicklous)
    Fix Version/s: 3.0.1

Fixed by Vernon in commit [ebdf0ef5f976106e59e9f84ae90e4966b4b7ceb7|https://github.com/apache/portals-pluto/commit/ebdf0ef5f976106e59e9f84ae90e4966b4b7ceb7]

> TCK: Contesting V2AddlFilterTests which assume getInitParameterNames returns parameters in a particular order
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-698
>                 URL: https://issues.apache.org/jira/browse/PLUTO-698
>             Project: Pluto
>          Issue Type: Bug
>          Components: tck
>    Affects Versions: 3.0.0
>            Reporter: Vernon Singleton
>            Assignee: Neil Griffin
>            Priority: Minor
>             Fix For: 3.0.1
>
>
> Neither the specification nor the Javadoc specify that PortletConfig.getInitParameterNames() should return parameters in any particular order. Yet, the tck assumes that they have a particular order [as of this commit 20a312be in master|[https://github.com/apache/portals-pluto/blob/20a312be1b0b180c105b190fd1d7b0f9a44f0ce1/portlet-tck_3.0/V2AddlFilterTests/src/main/java/javax/portlet/tck/portlets/AddlFilterTests_SPEC2_20_Filter.java#L140-L141].] 
> Since different portlet container implementations may return them in a different order, we propose a patch to the tck to ignore the order of the returned parameters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)