02-23-2009 10:53 AM
02-23-2009 11:10 AM
A sample JSF application has 2 pages, Page1.jspx and Page2.jspx.
The 'Page1.jspx' contains a button named 'GO' which has a action pointing/that will navigate to 'Page2.jspx'.
The user requests for Page1.jspx, the contents of the Page1 are rendered to the browser (Url: http://localhost:8989/Sample/faces/Page1.jspx)
When the user clicks on the Page1's 'GO' button, still the URL is Url: http://localhost:8989/Sample/faces/Page1.jspx, but the required navigation information is added in the postData().
Here, for processing, we are passing the URL along with the postData, but some how the http connection is not able to read the PostData contents properly.
Hence the new request results in the Page1 itself.
02-24-2009 06:35 AM
I have read some threads having the issue of 'viewState' in ASP.net. I think, JSF also uses the concept of 'ViewState', how this issue can be resolved for other applications that uses the 'ViewState' (other than ASP.NET).
02-25-2009 09:19 AM - edited 02-25-2009 09:19 AM