You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Robson Paniago de Miranda <rp...@gmail.com> on 2011/01/29 13:16:10 UTC
AjaxFormLoop does not render informal parameters
Hi,
I'm using AjaxFormLoop component in one of my projects, and I noticed that
this component does not render informal parameters.
There is some modification that could be made to the template of this
component that can allow it to render informal parameters (especially the
"class" attribute)?
BTW, I solved the problem described in bug TAP5-280 (
https://issues.apache.org/jira/browse/TAP5-280) by storing commands that
override the default behaviour of FormSupport, allocating new component ids
concatenated with the client value of the loop's value.
Att,
Robson Paniago
Re: AjaxFormLoop does not render informal parameters
Posted by Mark <ma...@xeric.net>.
> I'm using AjaxFormLoop component in one of my projects, and I noticed that
> this component does not render informal parameters.
I'm not sure why it isn't' rendering informal parameters. Others can
probably explain if this is a bug or by design. However, you can
usually work around this by just sticking another div with the desired
class inside of the AJaxFormLoop component.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: AjaxFormLoop does not render informal parameters
Posted by Robson Paniago de Miranda <rp...@gmail.com>.
Hi,
Since I didn't receive any feedback about this issue, I would like to know
if my approach to server validation and the problem with old values stale in
FormValidator was correct (i.e, to push an other implementation of
FormSupport which overrides the naming of the controls for each iteration,
based on the clientValue of the iterator).
Thanks,
Robson Paniago
2011/1/29 Robson Paniago de Miranda <rp...@gmail.com>
> Hi,
>
> I'm using AjaxFormLoop component in one of my projects, and I noticed that
> this component does not render informal parameters.
>
> There is some modification that could be made to the template of this
> component that can allow it to render informal parameters (especially the
> "class" attribute)?
>
> BTW, I solved the problem described in bug TAP5-280 (
> https://issues.apache.org/jira/browse/TAP5-280) by storing commands that
> override the default behaviour of FormSupport, allocating new component ids
> concatenated with the client value of the loop's value.
>
> Att,
> Robson Paniago
>
>