You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Jon Travis <jt...@p00p.org> on 2005/03/29 21:11:55 UTC
Re: Problem when decoding HtmlTextInput
Bouncing this to the dev list, since it seems like
more of a dev issue & getting no response on user.
-- Jon
On Mar 28, 2005, at 5:43 PM, Jon Travis wrote:
> I'm having a little problem which seems to have been
> recently introduced:
>
> I have some text inputs in my app, and it seems that
> the first time I retrieve the value from my backing
> bean they are outputted correctly to the browser.
>
> However, subsequent requests which should also pull
> values from the bean don't make those calls. From
> what I can tell, it looks like the following is
> happening:
>
> - HtmlRendererUtils is checking the value -- it gets
> (nothing was submitted), so it calls
> setSubmittedValue() on my input component with
> RendererUtils.EMPTY_STRING (which is "", not null)
>
> - Later, RenderUtils.getStringValue() is called
> (by HtmlTextRendererBase). This checks the submitted
> value and compares it against 'null.' If the value is
> null, it asks the backing bean for the value and displays
> that. What happens in reality, is that the value is
> "", so nothing is displayed.
>
> It's possible that my pages are screwed up, but this
> used to work and recently quit (we updated to new code
> to get some tree2 support.) Should the HtmlRendererUtils
> not use 'null' instead of "" for denoting no submitted
> value?
>
> -- Jon
Re: Problem when decoding HtmlTextInput
Posted by Heath Borders <he...@gmail.com>.
Whats happening is correct behavior, if the updateModelValues phase
doesn't complete.
If you have an immediate action on your page, or you want to force a
component to read from the backing bean, you need to manually set its
value and submittedValue to null and its localValueSet to false.
On Tue, 29 Mar 2005 11:11:55 -0800, Jon Travis <jt...@p00p.org> wrote:
> Bouncing this to the dev list, since it seems like
> more of a dev issue & getting no response on user.
>
> -- Jon
>
>
> On Mar 28, 2005, at 5:43 PM, Jon Travis wrote:
>
> > I'm having a little problem which seems to have been
> > recently introduced:
> >
> > I have some text inputs in my app, and it seems that
> > the first time I retrieve the value from my backing
> > bean they are outputted correctly to the browser.
> >
> > However, subsequent requests which should also pull
> > values from the bean don't make those calls. From
> > what I can tell, it looks like the following is
> > happening:
> >
> > - HtmlRendererUtils is checking the value -- it gets
> > (nothing was submitted), so it calls
> > setSubmittedValue() on my input component with
> > RendererUtils.EMPTY_STRING (which is "", not null)
> >
> > - Later, RenderUtils.getStringValue() is called
> > (by HtmlTextRendererBase). This checks the submitted
> > value and compares it against 'null.' If the value is
> > null, it asks the backing bean for the value and displays
> > that. What happens in reality, is that the value is
> > "", so nothing is displayed.
> >
> > It's possible that my pages are screwed up, but this
> > used to work and recently quit (we updated to new code
> > to get some tree2 support.) Should the HtmlRendererUtils
> > not use 'null' instead of "" for denoting no submitted
> > value?
> >
> > -- Jon
>
>
--
-Heath Borders-Wing
hborders@mail.win.org
Re: Problem when decoding HtmlTextInput
Posted by Heath Borders <he...@gmail.com>.
lol. Yeah, that would do it.
On Thu, 31 Mar 2005 15:52:01 -0800, Jon Travis <jt...@p00p.org> wrote:
> The problem with the totally bizarre behaviour
> I was getting is that there was a <verbatim>
> HTML form being used instead of a fancy JSF
> h:form...
>
> -- Jon
>
>
> On Mar 29, 2005, at 11:11 AM, Jon Travis wrote:
>
> > Bouncing this to the dev list, since it seems like
> > more of a dev issue & getting no response on user.
> >
> > -- Jon
> >
> >
> > On Mar 28, 2005, at 5:43 PM, Jon Travis wrote:
> >
> >> I'm having a little problem which seems to have been
> >> recently introduced:
> >>
> >> I have some text inputs in my app, and it seems that
> >> the first time I retrieve the value from my backing
> >> bean they are outputted correctly to the browser.
> >>
> >> However, subsequent requests which should also pull
> >> values from the bean don't make those calls. From
> >> what I can tell, it looks like the following is
> >> happening:
> >>
> >> - HtmlRendererUtils is checking the value -- it gets
> >> (nothing was submitted), so it calls
> >> setSubmittedValue() on my input component with
> >> RendererUtils.EMPTY_STRING (which is "", not null)
> >>
> >> - Later, RenderUtils.getStringValue() is called
> >> (by HtmlTextRendererBase). This checks the submitted
> >> value and compares it against 'null.' If the value is
> >> null, it asks the backing bean for the value and displays
> >> that. What happens in reality, is that the value is
> >> "", so nothing is displayed.
> >>
> >> It's possible that my pages are screwed up, but this
> >> used to work and recently quit (we updated to new code
> >> to get some tree2 support.) Should the HtmlRendererUtils
> >> not use 'null' instead of "" for denoting no submitted
> >> value?
> >>
> >> -- Jon
> >
> >
> >
> >
>
>
--
-Heath Borders-Wing
hborders@mail.win.org
Re: Problem when decoding HtmlTextInput
Posted by Jon Travis <jt...@p00p.org>.
The problem with the totally bizarre behaviour
I was getting is that there was a <verbatim>
HTML form being used instead of a fancy JSF
h:form...
-- Jon
On Mar 29, 2005, at 11:11 AM, Jon Travis wrote:
> Bouncing this to the dev list, since it seems like
> more of a dev issue & getting no response on user.
>
> -- Jon
>
>
> On Mar 28, 2005, at 5:43 PM, Jon Travis wrote:
>
>> I'm having a little problem which seems to have been
>> recently introduced:
>>
>> I have some text inputs in my app, and it seems that
>> the first time I retrieve the value from my backing
>> bean they are outputted correctly to the browser.
>>
>> However, subsequent requests which should also pull
>> values from the bean don't make those calls. From
>> what I can tell, it looks like the following is
>> happening:
>>
>> - HtmlRendererUtils is checking the value -- it gets
>> (nothing was submitted), so it calls
>> setSubmittedValue() on my input component with
>> RendererUtils.EMPTY_STRING (which is "", not null)
>>
>> - Later, RenderUtils.getStringValue() is called
>> (by HtmlTextRendererBase). This checks the submitted
>> value and compares it against 'null.' If the value is
>> null, it asks the backing bean for the value and displays
>> that. What happens in reality, is that the value is
>> "", so nothing is displayed.
>>
>> It's possible that my pages are screwed up, but this
>> used to work and recently quit (we updated to new code
>> to get some tree2 support.) Should the HtmlRendererUtils
>> not use 'null' instead of "" for denoting no submitted
>> value?
>>
>> -- Jon
>
>
>
>