On Fri, 23 Sep 2011 12:52:17 -0300, Muhammad Gelbana <m.gelb...@gmail.com> wrote:
I tried to have the most descriptive subject..that was my best shot
You succeeded. :)
*Index.tml* <t:select model="literal:a,b,c" value="select" t:id="select"/> *Index.page* @Property private String select; @Component(id="select") private *TextField* select
Again, it's obviously a tapestry user mistake, but should this raise an exception to point out what's wrong ?
I agree that Tapestry should raise an exception. Please file a JIRA for that. The wrong part was using @Component in your class at the same time as t:xxx or t:type="xxx". @Component serves to define/declare a component and the template part is supposed to only have the t:id and informal parameteres. If you want to get a component instance declared in the template, use @InjectComponent instead. So, fellow Tapestry users, please remember: @Component is not an annotation for injection, @InjectComponent is. :) -- 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-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
