Turned out Mixins are the perfect tool for this problem. They helped me to eliminate super.setupRender() calls in the beginning of every parameterized component setupRender().
Thanks for the clue, Thiago! On Sun, Jul 5, 2009 at 3:45 PM, Sergey Didenko<sergey.dide...@gmail.com> wrote: > Not yet. I needed that to refactor my current handling of request parameters. > > Right now I extend my base class ComponentWithParameters and then make > sure to call > > super.setupRender(); > > in the beginning of component setupRender() method. That is not very > elegant. Using a special annotation on setupRender() does not > eliminate this problem. I have to remember to "mark" setupRender() > anyway. > > So right now I just use the first approach. May be the better solution > would be to annotate the whole component class if it is possible to > advise component render methods. > > On Sun, Jul 5, 2009 at 1:03 AM, Thiago H. de Paula > Figueiredo<thiag...@gmail.com> wrote: >> Em Sat, 04 Jul 2009 04:33:10 -0300, Sergey Didenko >> <sergey.dide...@gmail.com> escreveu: > >> Have you already implemented what you needed? > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
