I didn't see Olof's original post, but this is what the PREPARE event is for.
Use it to set up the object that is being edited using the form context.
Also, note that there is a limitation with form validation. From the docs:
- tracker
- org.apache.tapestry.ValidationTracker
- defaultTracker
- pr
Hi,
oic, maybe an ajax will do? I am thinking of providing a hidden form, when
user click a link in one record, it will insert the hidden form below the
selected row for user to edit, then submit it via an ajax call and close the
form, not yet tried.
A.C.
"Olof =?UTF-8?Q?N=C3=A6ss=C3=A9n" ?=
I'm afraid not. I ended up with enclosing all users in one big form. I
thought it wasn't worth solving when the one form approach worked just
fine in my case.
/Olof
On 29/10/2007, Angelo Chen <[EMAIL PROTECTED]> wrote:
>
> Hi Olof,
>
> Did you find a solution to this? I have similar need as yours
Hi Olof,
Did you find a solution to this? I have similar need as yours this time.
A.C.
"Olof =?UTF-8?Q?N=C3=A6ss=C3=A9n" ?= wrote:
>
> I have a problem with using forms in components where the data model
> is passed to the components via parameter inside a T5 loop component.
> When a form is
This gets to be tricky stuff.
Remember that a form submissions starts with the page instance, with its
persisted fields rolled back to their latest values. Anything that isn't
@Persist will be in a null or default state.
What's going on here is that your form is dependent on same transitory
stat
