Yes, I'd clear both the local and submitted value. I wonder if setting immediate on the component might also have worked.
On 8/9/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
FYI, immediate on the action plus binding on UIInput with the following code worked: comp.setLocalValue(false); comp.setSubmittedValue(null); // not sure if this was necessary, but doesn't hurt. -Andrew On 8/4/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > On 8/4/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > One other solution I suppose is to use component binding and clear the > > submitted values on the component (or set them to the bean values). > > This one I may go with (if it works, haven't tried it yet). > > This is the approach I was going to suggest. > > The issue (I'm guessing) is that you're skipping conversion/validation > for the component much like using immediate=true. > > So you need to force the components to update the value. > I would clear both the submitted and local values, and at that point > during rendering, the component should pull in the backing bean > values. >
