Okay thanks, I already have my own custom view handler, so I should be able to handle the problem in it. I haven't switched to 1.2 yet as I don't yet feel that MyFaces 1.2 is stable enough for me yet and Trinidad 1.2.x is lagging behind 1.0.x and I am using functionality in 1.0.3.
-Andrew On 9/4/07, Adam Winer <[EMAIL PROTECTED]> wrote: > View expiry generally stinks in JSF 1.1; in 1.2, there's > a ViewExpiredException, so the user should currently > see an alert. That's not great - ideally, the main page > would refresh or redirect automatically. > > I'm disinclined to tackle view expiry in JSF 1.1, as it's > generally just badly broken there. > > -- Adam > > > On 8/31/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > Correct me if I am wrong, but it seems that if a view has expired, and > > someone initiates a partial update, the page is just updated as if it > > hadn't. This is quite confusing to the user as nothing happens when > > they click on a link. > > > > What I would like to have happen, is the user redirected to the > > requested view and be able to add a FacesMessage stating that the view > > had expired. > > > > Has anyone done this or is it built in somewhere and I have just missed it? > > > > Example: > > > > Go to the trinidad demo, go into the component demo. Walk away from it > > for a while. Click one of the links (like the component demo link). > > Nothing happens. A second click works (since now the user has a view > > in the back-end). > > > > Thanks, > > Andrew > > >
