--- 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.
IIRC as posted it was a local final variable in the method... There's no relationship created by that, it's for convenient access, declared final to avoid PEBKACs. All declaring it final does is make the compiler spew an error if the hapless programmer mistakingly does something like "context = foobar..." It does not affect the "framework's control" at all. d. ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
