Re: @Property limitations with java extensions

2011-05-13 Thread Clément Uster
> > > > This may cause a lot of pain ! >> > > I'm not following you . . . > > I just meant this won't be easy to manipulate generated DOM with java, but if it's the only way, I can deal with that. > > So, can I conclude that the use of @Property wouldn't be recommended >> within components ? Be

Re: @Property limitations with java extensions

2011-05-13 Thread Thiago H. de Paula Figueiredo
On Fri, 13 May 2011 12:52:36 -0300, Clément Uster wrote: Ok, I understand. Interesting approach, thanks. It's one of what I consider one of the hidden gems of Tapestry: its server-side DOM. This may cause a lot of pain ! I'm not following you . . . So, can I conclude that the use of

Re: @Property limitations with java extensions

2011-05-13 Thread Clément Uster
> > > 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

Re: @Property limitations with java extensions

2011-05-13 Thread Thiago H. de Paula Figueiredo
On Fri, 13 May 2011 11:53:19 -0300, Clément Uster wrote: Thanks Taha and Thiago. Hi! This is an old "corporate" lib, that isn't supposed to evolve anymore. This scenario isn't very good . . . It has a simple loop, and I want to change what is displayed for a particular index (by addin

Re: @Property limitations with java extensions

2011-05-13 Thread Clément Uster
Thanks Taha and Thiago. This is an old "corporate" lib, that isn't supposed to evolve anymore. 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"). 2011/5/13 Thiago H. de Paula Figueiredo > On Fri, 13

Re: @Property limitations with java extensions

2011-05-13 Thread Thiago H. de Paula Figueiredo
On Fri, 13 May 2011 10:37:18 -0300, Clément Uster wrote: Thanks for your very quick answer. :) :) What do you suggest if extending component isn't recommended ? Rewritting it ? In many scenarios you can solve problems by creating a mixin. Could you describe in more detail what you're

Re: @Property limitations with java extensions

2011-05-13 Thread Taha Hafeez
You can use composition Embed that component inside your component, and publish its properties. See the last topics of this page http://tapestry.apache.org/component-parameters.html regards Taha 2011/5/13 Clément Uster > Thanks for your very quick answer. :) > > What do you suggest if exte

Re: @Property limitations with java extensions

2011-05-13 Thread Clément Uster
Thanks for your very quick answer. :) What do you suggest if extending component isn't recommended ? Rewritting it ? I can't create getters and setters since the component belongs to another library. I guess this shouldn't happen if the component had more entry points. 2011/5/13 Thiago H. de P

Re: @Property limitations with java extensions

2011-05-13 Thread Thiago H. de Paula Figueiredo
On Fri, 13 May 2011 10:11:19 -0300, Clément Uster wrote: Hi everyone, Hi! Let's imagine I have a component (coming from a component library) that has an "index" property. So index has the @Property annotation. I want to create a component that extends the previous component. Extendin

@Property limitations with java extensions

2011-05-13 Thread Clément Uster
ot;index"'s value to change component's behaviour... how can I do this ? As long as "index" is private from the first component and there is no "getIndex()" method (thanks to @Property). Thanks ! Clément -- View this message in context: http://tapestry.1045711.