[ 
https://issues.apache.org/jira/browse/PLUTO-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357036#comment-16357036
 ] 

Vernon Singleton commented on PLUTO-686:
----------------------------------------

More tests call portletConfig.getContainerRuntimeOptions:
 * V2AddlPortletTests_SPEC2_6_RenderConfig_getContainerRuntimeOptions6
 * V2AddlPortletTests_SPEC2_6_RenderConfig_getContainerRuntimeOptions8

This fix for these was tested against master:
[https://github.com/ngriffin7a/portals-pluto/pull/21]

> 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: Neil Griffin
>            Priority: Minor
>             Fix For: 3.0.1
>
>
> 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)

Reply via email to