> > Again, you can't handle render events from other components. > I was just trying to explain the solution I tried to implement. I'll look into mixins then.
Thank you Robert and Thiago :) On Fri, Jul 1, 2011 at 11:27 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 01 Jul 2011 18:03:25 -0300, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > > The thing is that beaneditor encapsulates each rendered field in a div tag >> and I need to put more than one field in a single div tag so I need to >> handle the BeginRender event for the beaneditor. >> > > Again, you can't handle render events from other components. A component or > page class can only render its own render events. I guess your solution will > be to write a mixin and apply it to BeanEditor. And it will need to handle > the AfterRender, not the BeginRender one, which is triggered, obviouslly, > before BeanEditor starts rendering. > > > My case summerized, I have a beaneditor located inside a form (in the tml >> file). That form is in a page and I need to control who the fields tags >> are rendered by the bean. >> > > Grid, BeanEditor, BeanEditForm and BeanDisplay aren't meant to cover every > single scenario. > You can always declare the form field components yourself if BeanEditor > doesn't match what you want. Or provide your own template snippet for these > two fields. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- *Regards,* *Muhammad Gelbana Java Developer*
