Re: [OT] Re: Interceptor + putting information on the request

2007-03-07 Thread Matt Filion
purpose. Dave Newton <[EMAIL PROTECTED]> 03/07/2007 02:20 PM Please respond to "Struts Users Mailing List" To Struts Users Mailing List cc Subject Re: [OT] Re: Interceptor + putting information on the request --- Matt Filion <[EMAIL PROTECTED]>

Re: [OT] Re: Interceptor + putting information on the request

2007-03-07 Thread Dave Newton
--- Matt Filion <[EMAIL PROTECTED]> wrote: > Though the different situation seems like "overkill". I don't make my local vars 'final' either, but I know enough people that do. > How about expecting a programmer to look at the code > becore they modify it? :) Works great in theory ;) But seriou

Re: [OT] Re: Interceptor + putting information on the request

2007-03-07 Thread Matt Filion
such purpose. Dave Newton <[EMAIL PROTECTED]> 03/07/2007 02:01 PM Please respond to "Struts Users Mailing List" To Struts Users Mailing List cc Subject Re: [OT] Re: Interceptor

Re: [OT] Re: Interceptor + putting information on the request

2007-03-07 Thread Dave Newton
--- Matt Filion <[EMAIL PROTECTED]> wrote: > So for me it should be neither final or even a member > variable. Just a referance within the scope of the > executed method. > > It creates an unatural relationship that could > potential complicate the frameworks control of the > ActionContext. IIR

Re: [OT] Re: Interceptor + putting information on the request

2007-03-07 Thread Matt Filion
Dave, This is all symantics I guess, but I dont mind a good "discussion" :) To me with the way the relationship is between the 2 objects, ActionContext is not a PART of the Interceptor, it is something the Interceptor uses. So for me it should be neither final or even a member variable. Just a