Fair enough, it was a pretty jumbled structure and as a result difficult
to describe. Unfortunately I've moved on with my form separation method
(as you describe how you use dialog forms) which works well enough.
Essentially I had
<form>
<some form elements/>
<link onclick="async:load data into dialog and show it"/>
<submit onclick="sync:save form, dialog portion blank and ignored"/>
<dialog hidden="true">
<some form elements/>
<submit onclick="sync:save whole form including dialog part and
reload page"/>
</dialog>
</form>
Now, when I used the dialog submit the dialog's form elements were
submitting null/empty values. My theory was that when the dialog and
child components were re-rendered when the dialog was updated in the
async request, they were becoming detached form the original form.
Come to think of it, I wasn't specifying the component Id's (ie i was
just doing jwcid="@TextField") maybe if I specified an Id it would work?
Thanks for the interest jesse. does any of this make sense?
Jesse Kuhnert wrote:
I can't really piece together what you are doing vs. what is not
working as
expected but the Dialog component essentially does nothing other than
wrap a
block of html.
Tapestry does maintain form state during ajax requests - so if that's not
happening then something is wrong. It's possible that the client side
javascript code implementing the dialog moves the html nodes around in
such
a way that if you don't have a form within the dialog itself that the
nodes
will become separated from the original form and start to break
things. I
have always placed forms within my dialogs even when on pages with
"one big
form" as the placement of the dialog outside of the big form makes no
difference as the html displayed is always centered anyways.
Maybe an example would help but I just am not getting it looking at the
paragraphs of text.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
