How to avoid fetching pages twice
Hi, assume to browse through a long list of items (table, tree, etc.) by means of paging. Each JSF cycle needs the old page first (in Restore View), then the new one (in Render Response).
But if just browsing there is no need to update components, so the old page is not really needed. How to avoid this loading ? I know I could play with life-cycle events thus forcing the cycle to behave as we are always on a fresh view.
I just wonder if there is a cleaner solution to have render-only cycles.
Thanks -- Renzo
[538 byte] By [
Tomarenza] at [2007-11-26 15:13:42]
# 3
Hi,
You right. I was talking about the Update phase, which wasn't really the issue in the original post.
You cannot skip the restore_view/render_view but you can pay attention on the transient property of your components, specially in browsing-only cases.
This can significantly improve the processing of both phases.
The original post example *should* only have the next/previous (or whatever) as not transient to boost the restore_view/render_respose.
# 4
Thanks all. To clarify, my practical case came from a Trinidad tree, where I implemented the involved TreeModel to provide child paging by means of two dummy children (up/down arrow).
From debugging I noticed that twin loading effect while paging after arrow clicking. In this example a number of things have to be restored -such as tree expansion - which cannot be transient.
So far I understand that my only chance is to recognize the restore_ view phase by events, cutting off data loading till rendering time.
