Bridge does not remove the id of the PortletNamingContainerUIViewRoot from the list of execute and render ids from AjaxBehaviors

• 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.2-legacy-ga3, liferay-faces-3.0.3-legacy-ga4, liferay-faces-3.0.4-legacy-ga5, liferay-faces-3.0.0-ga1, liferay-faces-3.0.1-ga2, liferay-faces-3.0.2-ga3, liferay-faces-3.0.3-ga4, liferay-faces-3.0.4-ga5, liferay-faces-3.1.0-ga1, liferay-faces-3.1.1-ga2, liferay-faces-3.1.2-ga3, liferay-faces-3.1.3-ga4, liferay-faces-3.1.4-ga5, liferay-faces-3.2.4-ga5, liferay-faces-4.2.5-ga6
• Fix Version/s: liferay-faces-3.0.5-legacy-ga6, liferay-faces-3.0.5-ga6, liferay-faces-3.1.5-ga6, liferay-faces-3.2.5-ga6, liferay-faces-4.2.5-ga6
• Component/s: Liferay Faces Bridge Impl / Demos / Tests
• Labels: None

In most cases, instances of AjaxBehavior are created by the JSF runtime as a result of developers specifying the f:ajax tag handler. However, the new alloy:paginator component automatically submits forms via Ajax and has default values for the execute and render attributes. The default value for the render attribute is "@this @for" and the @for keyword corresponds to the clientId of the associated DataTable. This clientId is determined programatically, and in a portlet environment the clientId is prefixed with the id of the PortletNamingContainerUIViewRoot. In order for the JSF runtime's AjaxBehaviorRenderer to be able to successfully call UIComponent.findComponent(String) on the execute and render ids, the ids must have the id of the PortletNamingContainerUIViewRoot removed.