You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Joost Schouten (ml)" <jo...@jsportal.com> on 2011/07/25 15:01:30 UTC
Block response with form causes nested form exception where this
is not the case
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 component that renders formB in the Block to be returned lives
inside a formA.
Though slightly odd, this seems to me a valid usecase that should be
supported which would mean this is a bug. If I am missing something or
am just asking too much of tapestry, please tell me off :) If not, shall
I submit a bugreport?
Cheers,
Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Block response with form causes nested form exception where this
is not the case
Posted by "Joost Schouten (ml)" <jo...@jsportal.com>.
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 Hafeez wrote:
> 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 request. Perhaps we should also do that, in
> which case it will be a improvement.
>
> regards
> Taha
>
>
> On Mon, Jul 25, 2011 at 6:31 PM, Joost Schouten (ml)
> <jo...@jsportal.com> wrote:
>> 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 component
>> that renders formB in the Block to be returned lives inside a formA.
>>
>> Though slightly odd, this seems to me a valid usecase that should be
>> supported which would mean this is a bug. If I am missing something or am
>> just asking too much of tapestry, please tell me off :) If not, shall I
>> submit a bugreport?
>>
>> Cheers,
>> Joost
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Block response with form causes nested form exception where this
is not the case
Posted by Taha Hafeez <ta...@gmail.com>.
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 request. Perhaps we should also do that, in
which case it will be a improvement.
regards
Taha
On Mon, Jul 25, 2011 at 6:31 PM, Joost Schouten (ml)
<jo...@jsportal.com> wrote:
> 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 component
> that renders formB in the Block to be returned lives inside a formA.
>
> Though slightly odd, this seems to me a valid usecase that should be
> supported which would mean this is a bug. If I am missing something or am
> just asking too much of tapestry, please tell me off :) If not, shall I
> submit a bugreport?
>
> Cheers,
> Joost
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Block response with form causes nested form exception where this
is not the case
Posted by "Joost Schouten (ml)" <jo...@jsportal.com>.
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) 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 component that renders formB in the Block to be
> returned lives inside a formA.
>
> Though slightly odd, this seems to me a valid usecase that should be
> supported which would mean this is a bug. If I am missing something or
> am just asking too much of tapestry, please tell me off :) If not,
> shall I submit a bugreport?
>
> Cheers,
> Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org