Yes, that's what I thought, thanks for confirming. Kalle
On Mon, Aug 24, 2009 at 12:26 AM, Ulrich Stärk<u...@spielviel.de> wrote: > On 22.08.2009 19:38 schrieb Kalle Korhonen: >> >> Oh that - you need tell the bean editor that you want the field to be >> used in your form. See Property Editor Overrides at >> http://tapestry.apache.org/tapestry5.1/guide/beaneditform.html, e.g: >> >> <t:beaneditform object="formModel"> >> <t:parameter name="country"> >> <t:label for="country"/> >> <t:textfield t:id="country" value="formModel.country"/> >> </t:parameter> >> </t:beaneditform> >> >> Ulrich - in practice, is there a case when you would have to use >> @InjectComponent over @Component with T5? > > No, you don't /have/ to, at least I can't imagine a situation. If you are > giving your templates away to a designer you probably want to define all of > your component's parameters in the component class and then you have to use > @Component. You just have to realize that parameters defined within > @Component take precedence over those specified inside the template. Apart > from that @InjectComponent and @Component yield the same result. I believe > though, that it's good style to use @InjectComponent when you just want to > record a validation error for a specific field and don't want to actually > define a component. > > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
