[PLUTO-672] TCK: Contesting tests that expect JspException to be thrown when the copyCurrentRenderParameters attribute contains a non-boolean value

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.1
• Component/s: tck
• Assignee: Scott Nicklous
• Reporter: Neil Griffin (Inactive)
• Created: 07/Dec/17 22:20
• Updated: 14/Dec/22 14:37
• Resolved: 27/Feb/18 16:46

Description

The following tests have a try ... catch} block that assumes JspException will be thrown when invalid values are specified in portlet related tags.

For example:

<portlet:renderURL copyCurrentRenderParameters="invalid"/>

-
V2PortletTagLibraryTests2_SPEC2_26_IncludeJSPRender_actionURL22
-
V2PortletTagLibraryTests2_SPEC2_26_IncludeJSPRender_renderURL22
-
V2PortletTagLibraryTests3_SPEC2_26_IncludeJSPResource_actionURL22
-
V2PortletTagLibraryTests3_SPEC2_26_IncludeJSPResource_renderURL22

Pluto's implementation of portlet:renderURL defines the copyCurrentRenderParameters attribute as a String, whereas Liferay defines it as a boolean. In the case of Liferay, an invalid value like "invalid" is simply coerced to a boolean.

Since there is no requirement in the Portlet 3.0 Spec to throw JspException, recommend that the tests be removed from the TCK.