-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: bridge-impl-2.0.0, bridge-impl-3.0.0, bridge-impl-4.0.0
-
Fix Version/s: bridge-impl-2.1.0, bridge-impl-3.1.0, bridge-impl-4.1.0
-
Component/s: Liferay Faces Bridge Impl / Demos / Tests
-
Labels:None
Background:
The BridgePortletConfigFactory feature was introduced in FACES-2684 in order to provide a way for bridges to decorate the javax.portlet.PortletConfig object provided by the portlet container. Liferay Portal 7.0 and Pluto 2.0 do not require the object to be decorated, but Liferay Portal 6.2 does via the BridgePortletConfigFactoryLiferayImpl.java class in the liferay-faces-bridge-ext-3.x branch (see FACES-2819).
Because of this, there is a failure on TCK TestPage203 when running in Liferay Portal 6.2. The PortletConfig object that is saved as a request attribute in GenericFacesTestSuitePortlet.java is not the same as the PortletConfig object that is returned by the bridge's ELResolverImpl.java.
Steps to Reproduce:
- Deploy the Bridge TCK to Liferay Portal 6.2
- Visit http://localhost:8080/group/bridge-tck/testpage203
- Click Submit
Expected Result
Test: JSF_ELTest Status: SUCCESS Detail: JSF EL impicit objects correctly resolved in both action and render phases.
Actual Result
Test: JSF_ELTest Status: FAIL Detail: implicit object portletConfig resolved using the Faces EL resolver but its not equal to what is expected.
- is caused by
-
FACES-2819 I18nBridgeImpl throws NullPointerException when resource-bundle is omitted from portlet.xml in Liferay Portal 6.2
-
- Closed
-
- is fixed by
-
FACES-3097 Refactor workaround for FACES-2819 in order to fix FACES-2837
-
- Closed
-