[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-dev
Subject:    Re: Problem when decoding HtmlTextInput
From:       Jon Travis <jtravis () p00p ! org>
Date:       2005-03-31 23:52:01
Message-ID: 7fbee9ccc437e492c5156a96446f5281 () p00p ! org
[Download RAW message or body]

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
>
>
>
>


[prev in list] [next in list] [prev in thread] [next in thread]