[ https://issues.apache.org/jira/browse/PLUTO-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neil Griffin updated PLUTO-715: ------------------------------- Description: As described in PLUTO-687, the "javax.portlet.actionScopedRequestAttributes" {{container-runtime-option}} is an optional feature. The problem is that the TCK expects all portlet containers to support it: {code:java|title=AnnotationPortletApplicationConfigTests_SPEC1_28_EventConfiguration.java} @PortletApplication( runtimeOptions = { @RuntimeOption(name = "javax.portlet.escapeXml", values = { "true" }), @RuntimeOption(name = "javax.portlet.actionScopedRequestAttributes", values = { "true" }) } ... ) {code} {code:java|title=AnnotationPortletApplicationConfigTests_SPEC1_28_PortletContainerRuntimeOptions.java} if(runtimeOptions.containsKey("javax.portlet.escapeXml") && runtimeOptions.containsKey("javax.portlet.actionScopedRequestAttributes") && runtimeOptions.get("javax.portlet.escapeXml")[0].equals("true") && runtimeOptions.get("javax.portlet.actionScopedRequestAttributes")[0].equals("true")){ result.setTcSuccess(true); } {code} The proposal would be to use Maven profiles to control the build process, so that portal-specific (Pluto, WebSphere, Liferay) versions of the test can be supported. was: As described in PLUTO-687, the "javax.portlet.actionScopedRequestAttributes" {{container-runtime-option}}" is an optional feature. The problem is that the TCK expects all portlet containers to support it: {code:java|title=AnnotationPortletApplicationConfigTests_SPEC1_28_EventConfiguration.java} @PortletApplication( runtimeOptions = { @RuntimeOption(name = "javax.portlet.escapeXml", values = { "true" }), @RuntimeOption(name = "javax.portlet.actionScopedRequestAttributes", values = { "true" }) } ... ) {code} {code:java|title=AnnotationPortletApplicationConfigTests_SPEC1_28_PortletContainerRuntimeOptions.java} if(runtimeOptions.containsKey("javax.portlet.escapeXml") && runtimeOptions.containsKey("javax.portlet.actionScopedRequestAttributes") && runtimeOptions.get("javax.portlet.escapeXml")[0].equals("true") && runtimeOptions.get("javax.portlet.actionScopedRequestAttributes")[0].equals("true")){ result.setTcSuccess(true); } {code} The proposal would be to use Maven profiles to control the build process, so that portal-specific (Pluto, WebSphere, Liferay) versions of the test can be supported. > TCK: Contesting > AnnotationPortletApplicationConfigTests_SPEC1_28_PortletContainerRuntimeOptions > ----------------------------------------------------------------------------------------------- > > Key: PLUTO-715 > URL: https://issues.apache.org/jira/browse/PLUTO-715 > Project: Pluto > Issue Type: Bug > Components: tck > Affects Versions: 3.0.0 > Reporter: Neil Griffin > Assignee: Neil Griffin > Priority: Major > Fix For: 3.0.1 > > > As described in PLUTO-687, the "javax.portlet.actionScopedRequestAttributes" > {{container-runtime-option}} is an optional feature. The problem is that the > TCK expects all portlet containers to support it: > {code:java|title=AnnotationPortletApplicationConfigTests_SPEC1_28_EventConfiguration.java} > @PortletApplication( > runtimeOptions = { > @RuntimeOption(name = "javax.portlet.escapeXml", values = { "true" }), > @RuntimeOption(name = "javax.portlet.actionScopedRequestAttributes", > values = { "true" }) > } > ... > ) > {code} > {code:java|title=AnnotationPortletApplicationConfigTests_SPEC1_28_PortletContainerRuntimeOptions.java} > if(runtimeOptions.containsKey("javax.portlet.escapeXml") > && > runtimeOptions.containsKey("javax.portlet.actionScopedRequestAttributes") > && > runtimeOptions.get("javax.portlet.escapeXml")[0].equals("true") > && > runtimeOptions.get("javax.portlet.actionScopedRequestAttributes")[0].equals("true")){ > result.setTcSuccess(true); > } > {code} > The proposal would be to use Maven profiles to control the build process, so > that portal-specific (Pluto, WebSphere, Liferay) versions of the test can be > supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)