"why should we make a sessionscoped managedbean thread safe in jsf?" Code Answer

2

if you already worry about the threadsafety of the data in a certain scope, then the data most likely belongs in a more narrow scope (i.e. there is a flaw in the high level design). if the data is been put in the right scope, then there's totally no reason to worry about threadsafety. i assume that your beans are designed the right way that they aren't doing any business logic in the getters.

use the application scope for application wide data/constants, such as dropdown lists which are the same for everyone. use the session scope for client specific data, such as the logged-in user and user preferences (language, etc). use the view scope for rich ajax-enabled dynamic views (ajaxbased validation, rendering, etc). use the request scope for simple and non-ajax forms/presentations.

By TechTrip on September 13 2022

Answers related to “why should we make a sessionscoped managedbean thread safe in jsf?”

Only authorized users can answer the Search term. Please sign in first, or register a free account.