0

I have 3 different page where I use list of Users.

First page contains dataTable with users from one session scope managed bean. On that page I can change selected user details.

Second page also contains dataTable with users, but from different session scope bean. On this page I delete users from dataTable (list of users) and data base too.

I realized that this is not good idea, because if I made changes on one user, that changes will not be shown on page where I delete users.

Is application scope bean with only list of users a solution?

CallanSM
  • 303
  • 2
  • 10
  • 20

1 Answers1

1

Is application scope bean with only list of users a solution?

No, it won't solve the problem you're facing and you'll after all run into concurrency issues as a webapplication is usually a multi-user environment and you'd need to make everything synchronized to prevent nasty ConcurrentModificationException and like. An application scoped bean is namely shared between all users of the webapp. It makes no sense to hold request/view scoped data in an application scoped bean, even the session scope is too broad.

Your problem is thus that the session scope is too broad. You'd like to refresh the list on every fresh new GET request. Best to achieve this is to put the bean in the request or, better, view scope. The bean which edits the user detail could be another one, but this can in turn also easily be a just a property of the first bean whenever you don't want to make the edit page a bookmarkable GET request.

See also:

Community
  • 1
  • 1
BalusC
  • 1,082,665
  • 372
  • 3,610
  • 3,555