Just using ajax to update one form field should not wipe out all the other form fields, unless you add the entire form to your ajaxtarget. It is sufficient to only add the formcomponent you are updating to your ajaxtarget that way anything the user typed in will be preserved. Could you check if this is the case, and if not provide us with some code?
Maurice On Mon, Mar 3, 2008 at 10:01 PM, Gabor Szokoli <[EMAIL PROTECTED]> wrote: > Hi there, > > We have a regular form with an ajax modal window as popup helper for > populating one of the form fields, looks a bit like a datepicker. > Except the helper produces the form data in a non-trivial manner, > involving server roundtrip. > > The field does get populated nicely, but all entries in all other > fields on the same form are lost. > > What behavior should I put on what component to make form fields > silently persist their current, unsubmitted values to the server when > the modalwindow is opened? > > Any pointers would be aprechiated. > > And on top of that, some kind of general "roundtrip-less wicket for > the ajax illiterate" guide document would be nice. Something brief > enough as a javadoc to the wicket ajax package would suffice. > > We love wicket because we got by with it fine without substantial html > knowledge. > Until we stumbled into ajax. > Now we suddenly have to catch up on html, javascript, DOM, > xmlhttprequest, etc just to figure out what's what. > And then in the end the solution never involves any of that, just > passing the right thingie hadler as the whotsit to the doohickey. > > We still love it, just need some help :-) > > > Gabor Szokoli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
