Re: model update failing, I can't see why

2006-01-06 Thread Mike Kienenberger
Yeah, it's worth noting that inputHidden and saveState are very similar in behavior when used like this. On 1/5/06, Dennis Byrne [EMAIL PROTECTED] wrote: So, in cases where I need to output something, I know I'll have it there. Isn't what you're talking about only an issue if I go from a view

model update failing, I can't see why

2006-01-05 Thread Laurie Harper
I have this really weird problem I can't explain. I'm hoping someone can give me some insight. The problem is that my backing bean isn't being updated properly during the update model phase, *unless* I include a hidden input. With the source listed below it works fine, but if I remove the

Re: model update failing, I can't see why

2006-01-05 Thread Dennis Byrne
: Thursday, January 5, 2006 04:01 PM To: users@myfaces.apache.org Subject: model update failing, I can't see why I have this really weird problem I can't explain. I'm hoping someone can give me some insight. The problem is that my backing bean isn't being updated properly during the update model phase

Re: model update failing, I can't see why

2006-01-05 Thread Laurie Harper
parameter in the view ID, which is where I intend to end up to support bookmarking. L. -Original Message- From: Laurie Harper [mailto:[EMAIL PROTECTED] Sent: Thursday, January 5, 2006 04:01 PM To: users@myfaces.apache.org Subject: model update failing, I can't see why I have

Re: model update failing, I can't see why

2006-01-05 Thread Dennis Byrne
I'm not sure what you mean by 'conversation peice' but I think I understand what you're saying. The backing bean is in request scope and renderMode defaults to 'view' if there isn't a request parameter to set it to something else. So when the form is submitted and the component tree (re)built,

Re: model update failing, I can't see why

2006-01-05 Thread Laurie Harper
Dennis Byrne wrote: Er, a couple of times :-) Yes, it makes sense; either getDescription() will be called to render the outputText (view) or it will be called to render the inputText (edit). And because (without the hidden field) renderMode is effectively not preserved through the whole 'edit

Re: model update failing, I can't see why

2006-01-05 Thread Dennis Byrne
So, in cases where I need to output something, I know I'll have it there. Isn't what you're talking about only an issue if I go from a view with an input component to one that expects to display the input value, rather than validation returning to the same view that has the input component? What

Re: model update failing, I can't see why

2006-01-05 Thread Laurie Harper
Dennis Byrne wrote: So, in cases where I need to output something, I know I'll have it there. Isn't what you're talking about only an issue if I go from a view with an input component to one that expects to display the input value, rather than validation returning to the same view that has the