0 Replies Latest reply on Jun 8, 2011 3:58 PM by Thindenberg Thomas

    Bean providing @DataModel outlives navigation

    Thindenberg Thomas Newbie


      I have a Bean providing a @DataModel for a JSF dataTable, which works quite well.
      Because I need to preserve changes done by the user, the bean is Stateful with SESSION-scope. So when the user clicks on a table-entry, it stays highlighted.

      However, when I navigate to another page and back to the page with the table, which should now display different values, the bean is still alive of course, the data cached and I get the old data instead of new loaded.

      Is there any way I can force a reload of the @DataModel? Or to manually kill the left-over bean?

      Thanks, Clemens