NOTE: This article is an INTERNAL article and is not visible to customers, currently. Please only link this article in internal comments, but not public comments.
Issue
- After updating from de-32 to de-33, why is my custom portlet unresponsive after logging in? Opening a browser inspector shows that there are repeated network calls stuck in a loop ending in icefaces.ace.
Environment
- DXP 7.0
- Custom portlet implementing ICEfaces integration with a Liferay Faces Bridge
Resolution
- As portlet bridge standards and implementations evolved over time, Liferay Faces Bridge was created as the Reference Implementation (RI) for innovative features that make it possible to leverage the power of JSF 2.x inside a portlet application.
- If using this within a customized portlet, the Liferay-Faces-bridge impl version must be kept up to date to correspond with any API changes made across fix packs.
- In the case listed above, updating the Liferay-Faces-bridge impl to 4.1.1 resolved the unresponsiveness issue and restored portlet functionality.
Additional Information
- More information about which Liferay Faces artifacts should be used with a portlet can be found in this Help Center article.
-
As described in our Customizations Support Policy,
"Product defect resolutions such as patching will change the product code. If, by changing this code, custom development is adversely affected, then it is the responsibility of the customer to resolve the issue by adjusting the custom code. Liferay Support will assist in providing documentation concerning the product code changed as a result of installing a specific patch."