Portlet 3.0 TCK: Set character encoding via the setLocale method and a locale-encoding-mapping-list mapping in the web.xml deployment descriptor

• Type: Technical Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.0 DXP FP36, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, Master
• Component/s: None
• Labels:
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-36-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/54102

Test Result:

There is 1 failure in Portlet 3.0 TCK test V2AddlResponseTests:

Test case V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2: Details: The character encoding can be set via the setLocale method and a locale-encoding-mapping-list mapping in the web.xml deployment descriptor. Failed because character encoding is not "iso-8859-16" but UTF-8

Background:

According to Portlet Spec 3.0, Ch 15.7.1,

The portlet can set the character encoding for a resource response in several ways:

• Using the setCharacterEncoding method.
• Using the setContentType method. Calls to setContentType set the character encoding only if the given content type string provides a value for the charset attribute.
• Using the setLocale method and a locale-encoding-mapping-list mapping in the web.xml deployment descriptor. Calls to setLocale set the character encoding only if neither the setCharacterEncoding nor the setContentType method has previously set the character encoding.

In Liferay, the locale-encoding-mapping-list mapping in the web.xml deployment descriptor is not read. And in the setLocale method, the related code for setting character encoding is not implemented.