1 of 1 people found this helpful
because JSF navigation works using POST. It's one of the main problems which solved by some thirdparties and described in many blogs and finally adressed in JSF 2.
So some variants:
- just use redirect for navigation(will lost request data after redirect)
- check some custom solutions - e.g. richfaces-demo implements bookmarking and sources available in SVN (jboss.org/richfaces/demos)
- search for some small frameworks which solves this in general(prettyFaces if I'm not mistaken)
I see. So, if I upgrade to JSF 2.0 and use RF 3.3.3, the issue would be resolved?
not out of the box. JSF 2 also proposes to use special components h:link and h:button for that.
I think it's easier for you to just add redirect to your navigation cases if you not need to preserve request data after GET request which will be used in this case.
Sorry for delayed response, I just wasn't sure, if it would work for us, but it actually did quite well, since we had no need to preserve request data.
What if we did have it though?
Thanks a lot,
you will need to outject such data to some conversation or session scoped object