Make sure your managed beans have a small scope like @RequestScoped or @ViewScoped. Also, check that the data is updated in your database and you recover the list in page 2 from database and not from a session parameter.
–
Luiggi MendozaJan 24 '13 at 23:23

1)"page 2" is not a DOM element id so you cant address it the way you're attempting. 2)RequestContext is only valid for the current request, navigating to another page breaks the current request. 3)If a full page render,triggered by navigation, doesn't update your datatable, an ajax call won't update it. Your code has a fundamental problem that all the ajax tricks in the known universe will not overcome. Please post your code here if you need any assistance with it
–
kolossusJan 25 '13 at 1:13

@LuiggiMendoza I am using a '@SessionScoped' is that ok
–
user1817081Jan 25 '13 at 3:23

@user1817081 the problem will be that the bean will be stored in session, so when you revisit the page it won't create the bean which means that the list won't update it's values from calling to the database (at least that's how it must be if you follow JSF good practices as not having business logic in your getter/setter methods).
–
Luiggi MendozaJan 25 '13 at 3:52

Thanks. Do you know a good place to read over JSF good practice?
–
user1817081Jan 25 '13 at 13:55