-
1. Re: <managed-bean-scope> problem
rschoeler Nov 19, 2009 3:11 AM (in response to jsfgeeks)Hi jsfgeeks, one solution would be, before doing the going back:
1. get the session-bean
2. set the list/resultset of your extendedDataTable to null
3. reload the list from DB (or wherever you get your data)
This is the way in which I handle such scenarios.
It has the possibility that you have full control of refreshing data, but also the disadvantage that you must do this. Also you must be aware from the memory-consumption of such session-beans.
It would be nice to read from other possibilities to solve this problem.
At some time I've tried also to work with request-scope but I don't remember now, which are the reasons why I've switched the scope....sorry
regards rschoeler -
2. Re: <managed-bean-scope> problem
jsfgeeks Nov 19, 2009 11:31 PM (in response to jsfgeeks)Hi buddy,
Thanks for your support. I tried that also. But when I come back to the first page, then it gives error like,
javax.servlet.ServletException: duplicate Id for a component form1:extdtable_test:j_id55.
I have done like this,
I have created an object of first page(backbean). Then cleared arraylist which populates my table. Then called the function which fetches data from DB and populates the table. But I am getting the error mentioned above. In fact, I have provided id to all the columns and labels of all the columns. In short, I have provided id to all components. Then also it is giving same error.
Can you help me?
Thanks for your support,
JSF GEEKS