Mathias P.W Nilsson wrote:
This is what I do now. When Ajax onSubmit is ok I append a callback that
set's the forms action and post it.
Hmm okay, not completely what I meant. I'd rater make a clean panel with
markup containers where you set what you have and append that and submit
that instead.
I have also now, changed the name on submit so that works, ( ugly of course
) . Problem is the flickering
You'll get that because you need double post, you could hide the form on
submit..
I append javascript to the target on AjaxSubmitLink but it makes a sort of
post back first.
Yes. Because you need the validation to go thru, calling wicket first.
Because when I empty the cart before submitting the form I
see that the Listview is empty for a second.
Hmm, sounds like something else? Are you having a heartbeat or something
like it on your page?
If I append the javascript in
the decoration sequence then the validation never occurs.
No because you need it to first post to wicket.
This will only work if the user have javascript enabled.
Yes hence the javascript and AJAX bit. Otherwise you need for the user
to click twice, like once for validation and once for the real submit.
This could be okay too, you could then on the second submit just show
labels, and write that they now are validated and ask if they are sure
they want to submit this.
But I guess most
users do. I understand the problem with external post but I know there are
some wizards out there that could implement this. Maybe in the next wicket
release. External form?
Hmm an real external form would not have anything todo with wicket, you
could just have the form on the page without attaching it to wicket with
wicket:id's so no need for anything in wicket todo this.... Or I could
have gotten it wrong..
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
