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 -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
