-
Type:
Technical Task
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: 7.0.0 DXP FP35, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, Master
-
Component/s: None
-
Branch Version/s:7.0.x
-
Backported to Branch:Committed
-
Git Pull Request:
Test Result:
There are 3 failures in Portlet 3.0 TCK test V2AddlPortletTests:
V2AddlPortletTests_SPEC2_6_RenderConfig_getContainerRuntimeOptions7: Details: The returned Map contains values defined in the deployment descriptor <container-runtime-option> elements at the portlet level
V2AddlPortletTests_SPEC2_6_RenderConfig_getContainerRuntimeOptions8: Details: If the deployment descriptor contains <container-runtime-option> elements defined at both the portlet and the portlet application levels, the returned Map contains a merger of all values. Failed because runtime option javax.portlet.escapeXml is not found
V2AddlPortletTests_SPEC2_6_RenderConfig_getContainerRuntimeOptions9: Details: If the deployment descriptor contains <container-runtime-option> elements of the same name defined at both the portlet and the portlet application levels, the returned Map contains a the value defined at the portlet level
Background:
According to Portlet Spec 3.0, Ch 8.4,
The portlet can define additional runtime behavior in the portlet.xml on either the portlet application level or the portlet level with the container-runtime-option element. Runtime options that are defined on the application level should be applied to all portlets in the portlet application. Runtime options that are defined on the portlet level should be applied for this portlet only and override any runtime options defined on the application level with the same name.
Liferay doesn't read <container-runtime-option> defined at the portlet level at all. Liferay only reads those defined at the portlet app level.