-
1. Re: Urgent Guidance Requested – Dupli
liuliu Oct 21, 2009 6:47 AM (in response to paulbotta)maybe un status
-
2. Re: Urgent Guidance Requested – Dupli
ilya_shaikovsky Oct 21, 2009 8:21 AM (in response to paulbotta)seems that you have session scoped bindings.
-
3. Re: Urgent Guidance Requested – Dupli
paulbotta Oct 21, 2009 12:56 PM (in response to paulbotta)liuliu - Sorry, I don't know what you mean by un status. Can you tell me more?
-
4. Re: Urgent Guidance Requested – Dupli
paulbotta Oct 21, 2009 1:00 PM (in response to paulbotta)Ilya - After reading your response, I changed the bean scope to 'request' and restarted tomcat. I did not get the error, however, the page no longer functions as intended.
Are there any other work arounds, or is there a reference that you can point me to that would educate me in making a better design choice?
Thanks. -
5. Re: Urgent Guidance Requested ÃÂÂÂ
juangon Oct 21, 2009 2:15 PM (in response to paulbotta)There are a definitive solution for this: CLIENT state saving.
Only you have to do is changing a context-param from web.xml:<context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> </context-param>
Perhaps after this you could see some errors during testing (like not serializable classes etc), but itsn't usual.
This option has the great advantage of saving all the view state in client (in one hidden form field with name "javax.faces.ViewState" or something like that), better IMHO than saving it in session (javax.faces.STATE_SAVING_METHOD=server).
To solve the problems of the beans to keep their state between requests, we have several beans in request scope with a4j:keepAlive. With that, the state of that beans "travel" along the client and server. Some disadvantage of this is the network traffic, increasing it because all of the data that have to be sent in every request.
Some info about this:
http://www.jroller.com/mert/entry/state_saving_method_client_side -
6. Re: Urgent Guidance Requested – Dupli
paulbotta Oct 21, 2009 2:49 PM (in response to paulbotta)juangon - Thank you very much for your input and the education. I made the modifications, but I am still seeing the same issue. I must be doing something else wrong, but I am at a loss at how to troubleshoot it.
-
7. Re: Urgent Guidance Requested âÂÂÂ
nbelaevski Oct 21, 2009 2:59 PM (in response to paulbotta)"paulbotta" wrote:
Ilya - After reading your response, I changed the bean scope to 'request' and restarted tomcat. I did not get the error, however, the page no longer functions as intended.
Are there any other work arounds, or is there a reference that you can point me to that would educate me in making a better design choice?
Thanks.
What do you need component bindings for? -
8. Re: Urgent Guidance Requested – Dupli
paulbotta Oct 21, 2009 3:14 PM (in response to paulbotta)Hi nvelaevski -
There is a page where the user enters customer information. They can edit one that they have selected, or press a button to add a new customer. What I have found was if the user enters data that fails validation, and then hits 'cancel'. The data that failed validation doesn't reset. I was binding to the rich:inplaceInput components so that I could explicitly reset the values under the above scenario. -
9. Re: Urgent Guidance Requested – Dupli
nbelaevski Oct 21, 2009 5:19 PM (in response to paulbotta)I see. This should work fine with request-scoped beans either.
-
10. Re: Urgent Guidance Requested – Dupli
paulbotta Oct 21, 2009 10:25 PM (in response to paulbotta)I wanted to thank everyone who responded and got me in the right direction.
~Cheers