Forums de discussion

Bug in processing of public render parameters

thumbnail
Hubert Vogten, modifié il y a 12 années.

Bug in processing of public render parameters

New Member Publications: 11 Date d'inscription: 02/12/08 Publications récentes
We encountered a bug when dealing with public render parameters and the portletfaces-bridge-2.0.0. Under some circumstances the public render parameters were not picked up by the bridge. After some debugging, we found the problem in BridgeRequestScopeManagerImpl at line 207. According to the comment, the BridgeRequestScope must be removed from the cache so that a new one will be created. However, when either the new value or old value is null, the BridgeRequestScope is not removed from the cache.

Line 207: says:
if ((oldValue != null) && (newValue != null) && !oldValue.equals(newValue)) {

and should read as:
if (oldValue == null ? newValue != null : !oldValue.equals(newValue)) {

We tested the bridge with the new code and the public render parameters are now passed as expected.

Could you please fix this for the next release.
thumbnail
Neil Griffin, modifié il y a 12 années.

RE: Bug in processing of public render parameters

Liferay Legend Publications: 2655 Date d'inscription: 27/07/05 Publications récentes
Hi Hubert -- thanks for reporting this issue. Could you please create a bug in PortletFaces Bridge project in the issue tracker? http://issues.liferay.com/secure/Dashboard.jspa

That's would help us track this issue to closure. Thanks.
thumbnail
Hubert Vogten, modifié il y a 12 années.

RE: Bug in processing of public render parameters

New Member Publications: 11 Date d'inscription: 02/12/08 Publications récentes
Hi Neil,

I put the issue in JIRA. See http://issues.liferay.com/browse/FACES-237

Thanks