Taha,
Thanks. Personally I don't have a need for nested forms. I used them in
wicket before, found them somewhat usefull but do not miss them in
tapestry. As for my message, I was wrong and there actually was a nested
form which I missed initially.
Cheers,
Joost
On 25/07/11 3:28 PM, Taha H
Hi Joost,
Nested forms are not supported by html. Tapestry only enforces it.
When you render a block(containing a form) within a form, the
environmental FormSupport is pushed in twice so it will complains.
IMHO, it is not a bug. Other frameworks support nested forms by using
javascript based POST
My appologies. Tapestry was not to blame, it was me who overlooked
another little form stashed away in a dark corner of my application. Doh!
Joost
On 25/07/11 3:01 PM, Joost Schouten (ml) wrote:
Hi,
I have an EventLink that triggers an event method on a component
nested in a form (formA) a
Hi,
I have an EventLink that triggers an event method on a component nested
in a form (formA) and returns a Block with in it another form (formB) to
update a zone which is outside formA. Tapestry still complains about
formB being nested in formA. This is probably because of the fact that
the
