Return-Path: 
 <user-return-173350-apmail-struts-user-archive=struts.apache.org@struts.apache.org>
Delivered-To: apmail-struts-user-archive@www.apache.org
Received: (qmail 25808 invoked from network); 10 Jul 2007 12:13:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 10 Jul 2007 12:13:16 -0000
Received: (qmail 77678 invoked by uid 500); 10 Jul 2007 12:13:06 -0000
Delivered-To: apmail-struts-user-archive@struts.apache.org
Received: (qmail 77667 invoked by uid 500); 10 Jul 2007 12:13:06 -0000
Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@struts.apache.org>
List-Help: <mailto:user-help@struts.apache.org>
List-Post: <mailto:user@struts.apache.org>
List-Id: "Struts Users Mailing List" <user.struts.apache.org>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Delivered-To: mailing list user@struts.apache.org
Received: (qmail 77654 invoked by uid 99); 10 Jul 2007 12:13:06 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2007 05:13:06 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [85.214.44.140] (HELO e.nrgie.net) (85.214.44.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2007 05:13:02 -0700
Received: from webmail.nrgie.net (localhost [127.0.0.1])
	by e.nrgie.net (Postfix) with ESMTP id 502CCEFC0DA;
	Tue, 10 Jul 2007 14:36:16 +0200 (CEST)
Received: from 80.87.162.74
        (SquirrelMail authenticated user rene)
        by webmail.nrgie.net with HTTP;
        Tue, 10 Jul 2007 14:36:16 +0200 (CEST)
Message-ID: <47688.80.87.162.74.1184070976.squirrel@webmail.nrgie.net>
In-Reply-To: 
     <73896C9F08D68D438FCCBA8005C671E708A2E8CC@C3EXCHANGE.corp.premierinc.c
     om>
References: 
    <73896C9F08D68D438FCCBA8005C671E708A2E8CC@C3EXCHANGE.corp.premierinc.com>
Date: Tue, 10 Jul 2007 14:36:16 +0200 (CEST)
Subject: RE: [S2] Interceptor Question (Thread Safety)
From: "Rene Gielen" <gielen@it-neering.net>
To: "Struts Users Mailing List" <user@struts.apache.org>
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Checked: Checked by ClamAV on apache.org

I'll add some words on that to the docs.

Am Di, 10.07.2007, 13:42, schrieb Hoying, Ken:
> Thank you, Rene!
>
> This is a great help to me and allows me to move forward with my current
> implementation.  It might be a good idea for someone from the Struts2
> project to update the documentation with Rene's finding, as I am sure
> others will also find this unclear and concerning.
>
> Thank you again!
>
> -----Original Message-----
> From: Rene Gielen [mailto:gielen@it-neering.net]
> Sent: Tuesday, July 10, 2007 2:38 AM
> To: Struts Users Mailing List
> Subject: Re: [S2] Interceptor Question (Thread Safety)
>
> Ken, others,
>
> now for the definitive answer:
> There is one instance per interceptor ref, thus interceptor instances
> being unique within the scope they are referenced in.
>
> Example:
> <package name="foo" extends="struts-default" namespace="/foo">
>      <interceptors>
>          <interceptor name="foo" class="FooInterceptor"/>
>      </interceptors>
>      <action name="bar1" class="com.opensymphony.xwork2.ActionSupport">
>          <interceptor-ref name="foo">
>              <param name="bar">barfoobar</param>
>          </interceptor-ref>
>          <result name="success">/index.jsp</result>
>      </action>
>      <action name="bar2" class="com.opensymphony.xwork2.ActionSupport">
>          <interceptor-ref name="foo">
>              <param name="bar">barfoo</param>
>          </interceptor-ref>
>          <result name="success">/index.jsp</result>
>      </action>
> </package>
>
> This will cause two instances of FooInterceptor being created, one with
> bar property set to "barfoobar" and one with "barfoo". The interceptors
> parameters given in struts.xml are only set once per instance, which
> means that there are no thread safety issues with interceptor instance
> variables.
>
> HTH,
> Rene
>
>
> Rene Gielen schrieb:
>> Uahhh,
>>
>> thanks for pointing out this information, I was way to fast to reply
>> on the said question - I recalled it wrong. Indeed documentation is
>> right here, they need to be thread safe - sorry for causing
>> misunderstanding here.
>>
>> Anyway, this does not answer the question if interceptor parameters
>> introduce thread safety issues. The builder mechanism is a little
>> complicated here, but AFAIK Interceptor instances are unique to the
>> scope they are configured in. I will check this tonight to ensure we
>> do not face a problem here with current implementation and hopefully
>> can provide a reliable answer then.
>>
>> Regards,
>> Rene
>>
>> <interceptor name="
>>
>> Am Mo, 9.07.2007, 15:01, schrieb Hoying, Ken:
>>> Thanks, Rene!
>>>
>>> Someone might want to update the documentation to make this clearer.
>>> The following document seems to indicate otherwise:
>>>
>>> http://struts.apache.org/2.x/docs/writing-interceptors.html
>>>
>>> Thread Safety
>>> 	Interceptors must be thread-safe!
>>>
>>> A Struts 2 Action instance is created for every request and do not
>>> need to be thread-safe. Conversely, Interceptors are shared between
>>> requests and must be thread-safe.
>>>
>>> -----Original Message-----
>>> From: Rene Gielen [mailto:gielen@it-neering.net]
>>> Sent: Sunday, July 08, 2007 7:00 AM
>>> To: Struts Users Mailing List
>>> Subject: Re: [S2] Interceptor Question (Thread Safety)
>>>
>>> Ken,
>>>
>>> there is no problem at all since s2 interceptor instances, as well as
>
>>> action instances, are created per ActionInvokation, which means they
>>> are always operated in a single thread.
>>>
>>> Regards,
>>> Rene
>>>
>>> Hoying, Ken schrieb:
>>>> From what I understand from reading the documentation, interceptors
>>>> are suppose to be thread safe.  However, I have noticed that some of
>
>>>> the interceptors do  contain instance variables and I have seen some
>
>>>> examples where these variables are set or modified from with in the
>>>> action configurations.
>>>>
>>>> For example, the File Upload interceptor allows you to set the
>>>> maximumSize and allowedTypes.  Is this going to work if I have 2
>>>> different actions each allowing different maximumSize and
>>> allowedTypes?
>>>> This does not seem thread safe to me.  Is there only one instance of
>
>>>> the interceptors or does maybe each action mapping have its own
>>>> instance of the interceptors?
>>>>
>>>> Thanks in advance,
>>>> Ken
>>>>
>>>>
>>>>
>>>> -----------------------------------------
>>>> ***Note:The information contained in this message may be privileged
>>>> and confidential and protected from disclosure. If the reader of
>>>> this message is not the intended recipient, or an employee or agent
>>>> responsible for delivering this message to the intended recipient,
>>>> you are hereby notified that any dissemination, distribution or
>>>> copying of this communication is strictly prohibited. If you have
>>>> received this communication in error, please notify the Sender
>>>> immediately by replying to the message and deleting it from your
> computer. Thank you.
>>>> Premier Inc.
>>>
>
>
> --
> Rene Gielen  | http://it-neering.net/
> Aachen       | PGP-ID: BECB785A
> Germany      | gielen at it-neering.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>


--
Rene Gielen  | http://it-neering.net/
Aachen       | PGP-ID: BECB785A
Germany      | gielen at it-neering.net


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org