[
https://issues.apache.org/jira/browse/PLUTO-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391329#comment-16391329
]
Vernon Singleton commented on PLUTO-698:
----------------------------------------
This PR has been tested against the pluto tck master:
[https://github.com/ngriffin7a/portals-pluto/pull/24]
> 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: Scott Nicklous
> Priority: Minor
>
> 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)
