That would be a way to do it, but it's just as easy to put @SetupRender on A's setup render method. I usually rename it now to "preRender()" or something. All good.
On Sat, May 10, 2008 at 5:54 AM, Harald Geritzer <[EMAIL PROTECTED]> wrote: > Bill Holloway schrieb: > > > > I have two abstract component base classes A and B in the base > > package. B inherits from A. I have methods literally named > > "setupRender" in both. I notice that B's setupRender is called but > > not A's. *However*, if I rename A's setupRender() to some other name > > and annotate it with @SetupRender, both methods are called and in the > > correct order. > > > > as you are overriding the method in B, do you call super.setupRender() in > B? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Bill @ PeoplePad --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
