Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.0.0-ga1, 3.1.0-ga1
-
Fix Version/s: 3.0.0-legacy-ga1, 3.0.0-ga1, 3.1.0-ga1
-
Component/s: demos, liferay-faces-bridge
-
Labels:None
-
Similar Issues:
Description
The jsf2-ipc-pub-render-params-portlet demo has a WEB-INF/faces-config.xml descriptor that looks like this:
<bridge:public-parameter-mappings> <bridge:public-parameter-mapping> <parameter>selectedCustomerId</parameter> <model-el>#{customersPortlet:customersModelBean.selectedCustomerId}</model-el> <model-el>#{bookingsPortlet:bookingsModelBean.selectedCustomerId}</model-el> </bridge:public-parameter-mapping> </bridge:public-parameter-mappings>
But Section 5.3.1 of the Spec titled "Configuring a Public Render Parameter Mapping" indicates that instead, it should look like this:
<bridge:public-parameter-mappings> <bridge:public-parameter-mapping> <parameter>customersPortlet:selectedCustomerId</parameter> <model-el>#{customersModelBean.selectedCustomerId}</model-el> </bridge:public-parameter-mapping> <bridge:public-parameter-mapping> <parameter>bookingsPortlet:selectedCustomerId</parameter> <model-el>#{bookingsModelBean.selectedCustomerId}</model-el> </bridge:public-parameter-mapping> </bridge:public-parameter-mappings>
In summary, the namespace prefix should be specified in the <parameter> element rather than the <model-el> element. This will require not just a fix to the WEB-INF/faces-config.xml descriptor, but also to the bridge.
