[jira] [Commented] (PLUTO-686) TCK: Contesting tests that invoke portletConfig.getContainerRuntimeOptions
"Vernon Singleton (JIRA)" <[email protected]>
| Newsgroups | gmane.comp.jakarta.pluto.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/PLUTO-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345276#comment-16345276 ]
Vernon Singleton commented on PLUTO-686:
----------------------------------------
This fix was tested against the 3.0 tck on LR7 and pluto 3.
[https://github.com/ngriffin7a/portals-pluto/pull/18]
> TCK: Contesting tests that invoke portletConfig.getContainerRuntimeOptions
> --------------------------------------------------------------------------
>
> Key: PLUTO-686
> URL: https://issues.apache.org/jira/browse/PLUTO-686
> Project: Pluto
> Issue Type: Bug
> Components: tck
> Affects Versions: 3.0.0
> Reporter: Vernon Singleton
> Assignee: Vernon Singleton
> Priority: Minor
>
> The following tests assume that the portlet container will have the javax.portlet.servletDefaultSessionScope runtime option or they assume that will have at least 2 options:
> * V2PortletTests_PortletConfig_ApiRender_getContainerRuntimeOptions1
> * V2PortletTests_PortletConfig_ApiRender_getContainerRuntimeOptions2
> * V2PortletTests_PortletConfig_ApiRender_getContainerRuntimeOptions3
> Runtime options are options, so a container may not be forced to implement the javax.portlet.servletDefaultSessionScope option.
> The tck should be adjusted to allow each container to specify how many options it has for these checks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)