> I could make this error noticable by requiring that
> all components have an explicit id in the template
I think that the approach of making the framework smart enough to provide
useful default behaviours is always a good one. If anything is lacking at
the moment, it is just documentation to s
With the fresh start in T5 I've been able to make it smarter and more
adaptable, or at least, do better things by default. But there's a
lot of limits. I could make this error noticable by requiring that
all components have an explicit id in the template, but that would
inconvienience most users
D'oh! That's obvious now I look at it. Like most things in Tapestry, once you
have seen it once... :)
Thanks.
Howard Lewis Ship wrote:
>
>
> BeanEditForm is not a Form, but does own one; it includes a getForm()
> accessor. So:
>
> @Component
> private BeanEditForm _beanEditForm; // Case ju
You didn't supply a component id, so Tapestry did; your id is
"beaneditform" (matching the type of the component, converted to lower
case).
BeanEditForm is not a Form, but does own one; it includes a getForm()
accessor. So:
@Component
private BeanEditForm _beanEditForm; // Case just doesn't ma
That's what I thought, but when I tried it previously, I just got an
exception:
"Start does not contain an embedded component with id 'form'."
If I look at the source of the page that is generated without the
@Component, I see a form with id=form, so I don't know what is missing.
My page design
