[PORTLETBRIDGE-225] TCK assumption regarding portlet name

• Type: TCK Challenge
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.0
• Component/s: TCK
• Assignee: Michael Freedman
• Reporter: Neil Griffin
• Created: 21/Jul/12 16:08
• Updated: 14/Dec/22 15:09

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
portlet-bridge-tck-section3-2-lifecycle-set, v1.0.0
portlet-bridge-tck-section6-2-configured-response-wrapper, v1.0.0

[Exclude List Version]
N/A

[Test Name]

ALL tests in the TCK.

[Complaint (argument for why test is invalid)]

The JSR 329 TCK assumes that PortletConfig.getPortletName() returns the same value specified in the WEB-INF/portlet.xml portlet-name element. This is true for Pluto, but not for Liferay Portal.

For example, if the portlet-name is "chapter5_2Tests-isPostbackTest-portlet", then Liferay Portal will return "chapter5_2TestsisPostbackTestportlet". This causes all TCK tests to fail when running under Liferay Portal.

I'm filing this as a TCK Challenge because the Portlet API JavaDocs for PortletConfig.getPortletName()\http://portals.apache.org/pluto/portlet-2.0-apidocs/javax/portlet/PortletConfig.html#getPortletName() do not require that PortletConfig.getPortletName() be the same value specified in the portlet-name element.