I believe that you need to keep the logic for determining if only B should be updated in your submission listener, and use a hidden field/component to track the values last sent to the client. So if the user updates A + B, but only wants to store changes to B... You send everything back to the server, decide to only truly "keep" the change to B, and then scrape the original value for A from the hidden component and overwrite whatever value for A was updated in the rewind of the formm. This is probably clear as mud, because I'm wrestling with the same issues right now in my application and am having issues. Maybe someone on the list can help us determine if my recommendation has any merit or any major flaws. </bd>
________________________________ From: Theo vN [mailto:[EMAIL PROTECTED] Sent: Sat 7/8/2006 2:35 AM To: Tapestry users Subject: Re: Re: RE: RE: Re: Partial form submit Another possibility would be for the form processing cycle only to receive updated values for the parts specified - "old" values for fields A and C and "new"/updated values for field B? On 08/07/06, Theo vN <[EMAIL PROTECTED]> wrote: > The Tacos form works great. It can do a partial refresh for only on > the parts specified while it also updates the form component (updates > the hidden fields). What I am looking for (and maybe I'm naive) is a > partial form submit - in other words: if the form contains input > fields A, B, C then I want the ability to only post/submit the > contents of a defined part, say, containing only input field B and not > fields A or C - so the server only receives values for field B. > -- Regards Theo --------------------------------------------------------------------- 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]
