Wes Wannemacher wrote:
>
> On Wed, May 12, 2010 at 10:42 AM, Dale Newfield <d...@newfield.org> wrote:
>>
>> That all sounds reasonable, except the part about putting it in the
>> session
>> instead of the request. If there's no compelling reason to store
>> something
>> in the session, I think that it should be avoided. If you're using an
>> interceptor that's going to be doing this injection for each request
>> anyway,
>> you might as well store it in request scope.
>>
>> If you're storing it in the session, and the bean doesn't change much
>> (and
>> can't get stale), the interceptor might as well at least check to see if
>> it's already present and act as a no-op in that case.
>>
>
>
> Good point, Dale... I didn't read the OP close enough and was being lazy.
>
> -Wes
>
>
Thanks for all the replies so far folks.
Following up on that thought process, if I use an interceptor then is there
any difference/tradeoff/efficiency gain or loss from stuffing the object in
question onto the Value Stack instead of dropping it into the request or the
session? I guess that "explicitness" is what you gain from the
request/session route?
Later,
Andy
--
View this message in context:
http://old.nabble.com/Some-Spring-Struts-questions-tp28533505p28546199.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
