You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Werner Punz (JIRA)" <de...@myfaces.apache.org> on 2008/12/03 13:07:44 UTC
[jira] Created: (TRINIDAD-1328) PPR Cycle and single components
PPR Cycle and single components
-------------------------------
Key: TRINIDAD-1328
URL: https://issues.apache.org/jira/browse/TRINIDAD-1328
Project: MyFaces Trinidad
Issue Type: Improvement
Reporter: Werner Punz
The problem is, some components have to react on the javascript side depending on whether they are within a normal lifecycle or a ppr lifecycle.
The main issue is, that the ppr lifecycle does not trigger onLoads properly.
This is normal due to the fact that javascript has to be evaled.
You can bypass this by walking up the parents until the first component is found with Trinidad Triggers set and then use dom replace listeners to detect the PPR cycle.
This approach however is problematic from a performance standpoint, because every component has to walk up the tree
to detect the ppr points.
A better solution would be to set some App States on TrPage along the lines of TrPage.pprEval = true, TrPage.pprEval = false or something similar!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.