I know what the final keyword means :). I didn't tack it on there
because I thought it looked cool.
My question though is why does ognl care? From what little I could
tell it wasn't directly overriding my method calls. Rather it was replacing
them with calls to a proxy manager which was then redirecting them back to
the (wrapped) original class (Sort of like a java dynamic proxy but not
quite).
Is ognl actually *subclassing* my object in order to bolt on its own
accessor methods? Or is it constructing (as I assumed, perhaps erroneously)
a proxy of some sort?).
---- Pat
-----Original Message-----
From: Konstantin Ignatyev [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 26, 2005 9:49 PM
To: Tapestry users
Subject: Re: OGNL Voodoo
Very simple: final means that method can NOT be
overriden by subclasses.
http://www.allapplabs.com/interview_questions/java_interview_questions.htm#q
15
--- Patrick Casey <[EMAIL PROTECTED]> wrote:
>
>
> Does anyone have any insight into what's
> going on here? Why
> should finality of the method matter?
>
>
>
>
Konstantin Ignatyev
PS: If this is a typical day on planet earth, humans will add fifteen
million tons of carbon to the atmosphere, destroy 115 square miles of
tropical rainforest, create seventy-two miles of desert, eliminate between
forty to one hundred species, erode seventy-one million tons of topsoil, add
2,700 tons of CFCs to the stratosphere, and increase their population by
263,000
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a
Strategy for Reforming Universities and Public Schools. New York: State
University of New York Press, 1997: (4) (5) (p.206)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
