CONNER, BRENDAN (SBCSI) wrote:
That's a good point about redirect; we don't do that. ;-)
Regarding the "browser back" button, I believe that that works OK if you
set "client-side" state saving, rather than "server-side." Have you
tried that? We have to do "client-side" state saving anyway, because
otherwise JSF gets confused when we return from our pop-up windows.
No, this wont work.
If it comes to the point where a redirect will be issued due to the
navigation rule there is no chance for JSF to send data to the client.
The state on the client-side is rendered into the html-page.
Normally the flow is (very, very simplified):
1) Request
2) JSF
3) Your action code
4) you modify your request beans
5) the navigation rule will be applied
6) the new page will be rendered
In case of redirect it is:
1) Request
2) JSF
3) Your action code
4) you modify your request beans
5) the navigation rule will be applied
6) REDIRECT !!!! ->
7) NEW REQUEST (your "request beans" are lost now as we have a new request)
8) the new page will be rendered
Now the challenge it to save the beans (maybe marked with saveState)
during the transition from 6 to 7
---
Mario
