Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (nike.apache.org: domain of diostm@gmail.com designates
 209.85.213.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACgVPMxHE40OcKKLZqzirJv9qt8GpzPbTmN=63339T_SM0BfFA@mail.gmail.com>
References: <1A9CA81EFFD8434A9D15BC899F433A5B07A796@DLUMAIL03.sapient.com>
	<CACgVPMxHE40OcKKLZqzirJv9qt8GpzPbTmN=63339T_SM0BfFA@mail.gmail.com>
Date: Sat, 5 May 2012 00:16:51 +0300
Message-ID: 
 <CAFrzSN49HRB6CBhgN-MuetWZ2kfJ6uoB1kv103ZiX4azhP2ejg@mail.gmail.com>
Subject: Re: ActionContext and the application context
From: Dionis Argiri <diostm@gmail.com>
To: Struts Users Mailing List <user@struts.apache.org>
Content-Type: multipart/alternative; boundary=14dae9340a676dc74104bf3c7067

--14dae9340a676dc74104bf3c7067
Content-Type: text/plain; charset=ISO-8859-1

Good starting point would be reading code of action context etc, it could
give you some answers that are not mentioned in any
faq/tutorial/documentation. Simplified answer is - struts2 actions are
thread safe (but that doesn't means that if you inject some statefull
service in your bean, it'll be automatically thread safe). Reading source
code & debugging gave me the answer about session's internal
synchronization - SessionMap returned, that is thread safe wrapper around
non-thread safe HttpSession.

2012/5/4 vEnkaTa mohAna rAo SriperumbUdUru <mohanaraosv@gmail.com>

> Go through this link
>
> http://stackoverflow.com/questions/10296108/struts2-actioncontext-and-valuestack
>
>
> On Fri, May 4, 2012 at 11:18 AM, Puneet Babbar 2 <pbabbar2@sapient.com
> >wrote:
>
> > Hi,
> >
> > I have slight confusion in understanding of the thread locality of the
> > ActionContext. And action context contains the application, session,
> > request... etc
> >
> > Talking about general servlet/jsp programming, anything set in the
> > application context can be shared between different sessions or users.
> >
> > So since ActionContext is thread local(which means that values stored in
> > the ActionContext are unique per thread).
> > So, what is the impact on application context? Since its accessed using
> > ActionContext.
> >
> > Regards
> >
> > Puneet babbar
> >
> >
>

--14dae9340a676dc74104bf3c7067--