Because it depends on how dynamic the list is. I only have a few things which are so unchanging from user to user and screen to screen that they can go in application scope.

But I use the same mechanism for the objects in request scope that are lists which depend on an ID or something and so change from request to request.

One of the parameters to the method takes an int which could be any of PageContext.APPLICATION_SCOPE, SESSION_SCOPE or REQUEST_SCOPE.

Adam

Rick Reumann wrote:
On Tue, Jul 15,'03 (04:04 PM GMT+0200), Adam wrote:

Since it's in my action base class, I never have to worry about programming it manually.


If you are always going to check that the List is there in your
BaseAction class, why not just give the List application scope on start
up and not have to worry about checking for it?





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to