what strategy for javabeans in session/request scope ?

[Nicolas De Loof <ni...@capgemini.com>]

Hello,

I've worked on some applications using Struts and I haven't fond a definitive response to this :

When a webapp uses some javabeans on many pages (as an example, a List of beans and some sorting/paging actions), it is
better to :

- put the list in session scope (but then, how to remove it ?)
- call the model on every request (model should then use caching)
- any other ?

Thanks for help.

Nico.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org