You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Titi Wangsa <bl...@gmail.com> on 2007/03/01 03:24:22 UTC
Re: [Solved] Never before seen exception (facelets.FaceletViewHandler handleRenderException) - ??
i had the exactly same problem with oscache <cache></cache>
because the first time the page loads, it gets rendered properly, second
time it loads there were some parts that were cached.
i think that happens when some of the jsp gets rendered conditionally.
besides jsf, what other components/libraries are in you jsp page?
of just three taglibs <f:></f:> and <h:></:h> and <t:></:t>
Re: [Solved] Never before seen exception (facelets.FaceletViewHandler handleRenderException) - ??
Posted by Titi Wangsa <bl...@gmail.com>.
from what i understand, ehcache page caching uses a filter. try no to use
the filter and see what happens..
my guess is that the first time you request the page, the filter does not
have a cached copy
and process the page properly.
the second request, the page is already in the cache, some components get
rendered, some do not. First render ( cached(item1), item2). Second render
(item2). But item2 gets rendered with id item1.
another painful seguestion is to have all, all as in every component to have
id="xxx", this is to prevent jsf from generating the id so its does not
matter if you cache it or not.
i'm probably shooting in the dark here.