ansaurus

Question

javax.faces.application.ViewExpiredException: View could not be restored.

Answer 1

+1 A:

The ViewExpiredException will be thrown whenever you submit a HTTP POST request using h:commandLink or h:commandButton while the associated view isn't available in the session anymore. Redirecting the request after logout is not the only solution, you also need to disable the browser cache. Otherwise browser is displaying page from cache. If you're using POST for navigation, this will in turn fail (the view ID is namely stored as hidden input field of POST form).

To fire a redirect after logout in JSF 2.0, either add <redirect /> to the <navigation-case> in question (if any), or add ?faces-redirect=true to the outcome value.

<h:commandButton value="Logout" action="logout?faces-redirect=true" />

or

public String logout() {
    // ...
    return "index?faces-redirect=true";
}

To disable the browser cache, create a Filter which is mapped on the url-pattern of interest (e.g. *.jsf) and contains the following in the doFilter() method:

response.setHeader("Cache-Control", "no-cache, no-store, must-revalidate"); // HTTP 1.1.
response.setHeader("Pragma", "no-cache"); // HTTP 1.0.
response.setDateHeader("Expires", 0); // Proxies.
chain.doFilter(request, response);

When you want to handle the ViewExpiredException on an arbitrary page which was already opened in some browser tab/window while you're logged out in another tab/window, then you'd like to specify an error-page for that in web.xml which goes to index/login page. E.g.

<error-page>
    <exception-type>javax.faces.application.ViewExpiredException</exception-type>
    <location>/login.jsf</location>
</error-page>

That said and unrelated to the problem, using HTTP POST for pure page-to-page navigation isn't very user/SEO friendly. In JSF 2.0 you should really prefer h:link or h:button over the h:commandXXX ones for plain navigation.

BalusC 2010-09-04 15:57:25

How can I do it with implicit navigation in java ee 6? I don't use faces-config.

l245c4l 2010-09-04 16:01:57

Oh, you're using JSF 2.0? You should have mentioned that in your question! Add `?faces-redirect=true` to the `outcome`. I've updated the answer accordingly.

BalusC 2010-09-04 16:02:44

Yes I just started with java ee:) and I'm using faces-redirect=true in all my navigations. I use h:commandLink only when I have actions assosciated with it. For example Logout link... I have action String logout() where I invalidate session and redirect to login, but it doesn't work on page where I was logged in and being at the moment logged out and throws that exception :(

l245c4l 2010-09-04 16:13:29

As said, only redirecting is not enough. You also need to disable browser cache. Btw: in Java EE 6 you can use `@WebFilter` to register the filter. Update: I think I understand your new problem, you want to handle it for an arbitrary already-opened page as well? See the answer update.

BalusC 2010-09-04 16:22:00

Okay I created filter DisableBrowserCacheFilter did all setXXXXX but it still gives me this error. On page where I'm actually logging out it redirects me to login but on other pages still that error. Actually I'm binding this filter to "/*" url pattern. Is it good?:) I have already another filter with same pattern (to switching between https and http) so maybe they are conflicting?

l245c4l 2010-09-04 16:33:44

Honestly said, I find it hard to understand your *actual* problem about *"on other pages still that error"*, since you didn't describe the use case in detail. But I already made a guess about that, have you checked the updated answer about the error page? By the way, mapping filter on `/*` is a bit too wide. You would of course like to allow cache for static files (css, js, img, etc) to save network bandwidth.

BalusC 2010-09-04 16:43:04

Yeah exactly what I was thinking. I've already made it with error-page but I thought that exception showing that something bad is happening:) Thanks for your answers. I hope you can help me next time too:)

l245c4l 2010-09-04 16:47:11

You're welcome.

BalusC 2010-09-04 16:54:48

BTW I've created Session Expired error page bound to that exception. Now it would be good idea to redirect from there to index or login. How do I do that in JSF 2.0 ? Another filter with some 'sleep' would be good idea?

l245c4l 2010-09-04 17:02:04

A `<meta http-equiv="refresh" content="3;url=login.jsf">` in `<head>` goes to `login.jsf` after `3` seconds. For future new question please press `Ask Question` button :)

BalusC 2010-09-04 17:07:16

Thanks again and sorry for that:) but at least I got quick and professional answer in no time :p

l245c4l 2010-09-04 17:16:46

ansaurus

tags:

views:

answers:

javax.faces.application.ViewExpiredException: View could not be restored.

related questions