[PORTLETBRIDGE-226] requestProcessingNonFacesTest specifies charset in JSP

• Type: TCK Challenge
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.1, 3.0.0
• Component/s: TCK
• Environment: Liferay Portal + Liferay Faces Bridge
• Assignee: Michael Freedman
• Reporter: Neil Griffin (Inactive)
• Created: 24/Jul/12 22:34
• Updated: 14/Dec/22 14:37
• Resolved: 01/Aug/12 23:19

Description

[Test Challenger Name and Company]
Neil Griffin, Liferay, Inc.

[Specification Name(s) and Version(s)]
Portlet 2.0 Bridge for JavaServer™ Faces 1.2

[Test Suite Name and Version]
portlet-bridge-tck-main, v1.0.0

[Exclude List Version]
N/A

[Test Name]
requestProcessingNonFacesTest

[Complaint (argument for why test is invalid)]

If the TestPage017 (requestProcessingNonFacesTest) is successful, the output text should be the following:

Detail: Expected response content type is text/html, actual value is text/html.

However, under Liferay Portal the test fails with the following:

Detail: Expected response content type is text/html, actual value is text/html; charset=UTF-8.

The reason why is because the test contains a JSP file named chapter4_2_5Result.jsp that starts with the following directive:

<%@ page contentType = "text/html; charset=UTF-8" ... %>

... and Liferay Portal has a feature that respects the contentType attribute of the page directive, which ultimately calls back into the Liferay implementation of MimeResponse.setContentType(String). That's why Liferay returns an actual value of "text/html; charset=UTF-8"