-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: liferay-faces-3.0.0-legacy-ga1, liferay-faces-3.0.1-legacy-ga2, liferay-faces-3.0.0-ga1, liferay-faces-3.0.1-ga2, liferay-faces-3.1.0-ga1, liferay-faces-3.1.1-ga2
-
Fix Version/s: liferay-faces-3.0.2-legacy-ga3, liferay-faces-3.0.2-ga3, liferay-faces-3.1.2-ga3
-
Component/s: Liferay Faces Bridge Impl / Demos / Tests
-
Labels:None
The icefaces3-portlet was originally developed back when ICEfaces 2.0 was released. At the time, I don't think there was any feature to automatically disable ajax on a page-by-page basis.
Since the portletPreferences.xhtml composition was auto-ajaxified by ICEfaces, the PortletPreferencesBackingBean class was not able to execute the following code without getting a ClassCastException to ResourceResponse:
ActionResponse actionResponse = (ActionResponse) externalContext.getResponse(); actionResponse.setPortletMode(PortletMode.VIEW); actionResponse.setWindowState(WindowState.NORMAL);
Since we have an overarching goal of having all of the Job Applicant demo portlets (JSF2, ICEfaces, PrimeFaces, RichFaces) contain all of the same features, we need to enable navigation again. This can be achieved by putting back the aforementioned Java code back into the PortletPreferencesBackingBean class, and also adding the following command to the portletPreferences.xhtml composition:
<icecore:config render="false"/>