It's not quite true, but close enough.
All form components have to have a FormSupport environmental object
available when they render. So you can have form fields that are in
blocks on non-rendering pages and pull those blocks into the rendering
page and everything works fine. The problem occurs when you do an
ajax request where you want to update some small portion of the page,
itself contained within a form, with some form-based content. In that
case, the "naive" solution will fail. Eg:
<t:form>
...
<t:zone ...><!-- some zone to be updated via ajax, within the form;
we want it to render form fields. --></t:zone>
...
</t:form>
When you update the zone with some form-field-containing content,
you'll get a failure because the form fields won't have a FormSupport
object available to them in the environment.
This is what, eg, the FormInjector component tries to solve.
Unfortunately, it seems geared toward use with, eg, AjaxFormLoop. In
any event, it's a bit unwieldy to use on its own.
Robert
On Jan 21, 2010, at 1/219:35 AM , Andreas Andreou wrote:
On Thu, Jan 21, 2010 at 16:47, Inge Solvoll
<inge.tapes...@gmail.com> wrote:
This limitation has been a blocker for me too. All form components
need to
be enclosed by a form in the same template.
Is that true? Anyone knows if there's a reason for this? Cause
otherwise, you should
file a bug report
---------------------------------------------------------------------
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
