[
https://issues.jboss.org/browse/GTNPORTAL-2479?page=com.atlassian.jira.pl...
]
Vu Viet Phuong commented on GTNPORTAL-2479:
-------------------------------------------
I've found the problem, the above code expects to use the "each" function
that is defined in prototype.js in richfaces-impl.jar not the one in Gatein' Util.js
On GateIn 3.2, the Util.js file is in merged.js and this file always be loaded first. Then
the scripts in RichFaces demo portlet override Array.each function
GateIn 3.3, we introduce lazy loading machanism for javascript. There is no merged.js
anymore, an the Util.js is now lazy loaded --> RichFaces portlet can't override
Array.each function anymore --> raise js exception when it run into wrong
"each" function
JSF Portlet page doesn't re render after Ajax ActionRequest
-----------------------------------------------------------
Key: GTNPORTAL-2479
URL:
https://issues.jboss.org/browse/GTNPORTAL-2479
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.3.0.Final
Environment: GateIn 3.3 on AS5 or AS7, with JSF and RichFaces
Reporter: Ken Finnigan
Priority: Blocker
Fix For: 3.4.0.Final
Deploying a RichFaces/JSF portlet to GateIn, with JBoss PortletBridge, no longer
correctly handles Ajax menu navigation.
In GateIn 3.2 selecting a menu option in the RichFaces demo would redisplay the portlet
with new content in the right hand section of the portlet. In GateIn 3.3 clicking the
menu option has no impact, however, refreshing the page then does display the correct
content.
It appears that between GateIn 3.2 and 3.3 there was a change to how Ajax action requests
are handled such that it doesn't result in an update to the portal page without an
entire page refresh.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira