Neil Griffin created PLUTO-734:
----------------------------------
Summary: TCK: Contesting
AnnotationPortletAppConfigOverrideTests_SPEC1_28_PortletContainerRuntimeOptions
Key: PLUTO-734
URL: https://issues.apache.org/jira/browse/PLUTO-734
Project: Pluto
Issue Type: Test
Components: tck
Affects Versions: 3.0.1, 3.0.0
Reporter: Neil Griffin
Assignee: Neil Griffin
Fix For: 3.0.2
Similar to PLUTO-715,
AnnotationPortletAppConfigOverrideTests_SPEC1_28_PortletContainerRuntimeOptions
assumes that all implementations of Portlet 3.0 will support the following
runtime options:
{code:java|title=
AnnotationPortletAppConfigOverrideTests_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 problem is that the {{javax.portlet.actionScopedRequestAttributes}}
container-runtime-option is optional.
Similar to the solution for fixing PLUTO-715, this issue serves as a task for
introducing "pluto" and "liferay" maven profiles that account for the
differences.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
