field variables related to the internal
> processing of the class? i.e.. i have field variables only related to the
> param tags only and nothing more. Now is the interceptor thread safe?
>
> Kindly clarify.
>
>
>
> --
> View this message in context:
> http://www.nabb
the class? i.e.. i have field variables only related to the
param tags only and nothing more. Now is the interceptor thread safe?
Kindly clarify.
--
View this message in context:
http://www.nabble.com/Interceptors-and-Thread-safety-tp24391223p24391223.html
Sent from the Struts - User mailing lis
Now I'm even more confused about where dependency injection happens for
interceptors.
My long running process is importing large numbers of documents into my
system (extracted from an uploaded .zip file), which needs DB access
throughout the process. As such, I use something based upon:
htt
On 4/17/07 5:38 AM, "Dave Newton" <[EMAIL PROTECTED]> wrote:
> --- Dale Newfield <[EMAIL PROTECTED]> wrote:
>> [...] so that implies only a single simultaneous use
>
>> of a single execAndWait action per login?
>
>> From the execAndWait JavaDoc:
>
> """
> This interceptor works on a per-session
--- Dale Newfield <[EMAIL PROTECTED]> wrote:
> [...] so that implies only a single simultaneous use
> of a single execAndWait action per login?
>From the execAndWait JavaDoc:
"""
This interceptor works on a per-session basis. That
means that the same action name (myLongRunningAction,
in the abov
Laurie Harper wrote:
Likewise, should two different users both calling an execAndWait
action be able to co-exist, or will they mess with each other up?
One would hope the former ;-) execAndWait obeys the thread-safety
requirement, so there shouldn't be any collisions on a
request-by-request b
Dale Newfield wrote:
Shahak Nagiel wrote:
This was my concern exactly; Is a separate interceptor instance shared
among all references to each action, or more broadly just a
Struts-wide singleton?
For example, if you configure an execAndWait for both actions "foo"
and "bar", with delays of 2
Dave Newton wrote:
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
Shahak Nagiel wrote:
So, how can these [interceptors] be thread-safe if
new Interceptors aren't being instantiated for
every
request?
Because the parameters don't come from (or vary
with) the request.
Just to add on/clarify a
Shahak Nagiel wrote:
This was my concern exactly; Is a separate interceptor instance shared among
all references to each action, or more broadly just a Struts-wide singleton?
For example, if you configure an execAndWait for both actions "foo" and "bar",
with delays of 2 and 4, respectively, wi
MAIL PROTECTED]>
To: Struts Users Mailing List
Sent: Monday, April 16, 2007 6:33:03 AM
Subject: Re: Interceptors and thread-safety
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
> Shahak Nagiel wrote:
>> So, how can these [interceptors] be thread-safe if
>> new Interceptors aren
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
> Shahak Nagiel wrote:
>> So, how can these [interceptors] be thread-safe if
>> new Interceptors aren't being instantiated for
every
>> request?
> Because the parameters don't come from (or vary
> with) the request.
Just to add on/clarify a little bit
Shahak Nagiel wrote:
The "Writing Interceptors" guide pretty clearly states that "Interceptors are shared between requests
and must be thread-safe." However, there are some Interceptors--such as execAndWait and roles--which accept
parameters (e.g. "delay" and "allowedRoles") and which, ostens
12 matches
Mail list logo
