> > > This is an old "corporate" lib, that isn't supposed to evolve anymore. >> > > This scenario isn't very good . . .
Indeed... The component was frozen with tapestry 5.1.0.5 and the need was too urgent to wait for a release. But, ok ! No worries. :) > > It has a simple loop, and I want to change what is displayed for a >> particular index (by adding an "if" component, testing the value of >> "index"). >> > > I'd use a mixin which has a afterRender(MarkupWriter writer) and then > change the Tapestry DOM. It's not easy nor particularly elegant, but this is > a workaround for using a component that can't be changed without rewriting > it. This technique has saved my day many times. > > > Ok, I understand. Interesting approach, thanks. This may cause a lot of pain ! So, can I conclude that the use of @Property wouldn't be recommended within components ? Because (even with mixins) you may want to have access to some properties of the component... Or do you have a better practice ?
