Title: Best practices for choosing managed bean scope

What are the best practices for choosing managed bean scope? In the past, I have been avoiding session scope in favor of request scope for obvious reasons (memory requirements, no need for session failover etc). But I see that many JSF examples put beans in session scope without explaining why this is needed. For example, the Trinidad TreeTable demo puts its managed beans in session. Is this really necessary? Are there any best practices in trying to decide the scope of managed beans?

Thanks.
Naresh

Reply via email to