Aaron,
This seems like a popular problem with JSF. I'll assume you're using a value-binding for the value of your component. What we're doing when we want the page to refresh it's value from the backing bean is to just do component.setValue(null), and component.setSubmittedValue(null)
Give that a whack. Would be nice to have a 'best practices' or FAQ page for JSF developers -- stuff like this would sit at the top.
-- Jon
On May 18, 2005, at 2:09 PM, Aaron Bartell wrote:
I have looked into this some more and am trying to figure out what determines when a object that extends HtmlInputText will have the getter property called for each round trip to the server. Is there a setting some where that makes it so <x:inputDate> (a.k.a. HtmlInputCalendar) doesn't have it's getter property called for subsequent round trips after the initial page load?
I started looking at the MyFaces code base, but couldn't find where that would be specified. From what I can tell here is the inheritance structure:
javax.faces.component.UIOutput javax.faces.component.UIInput javax.faces.component.html.HtmlInputText org.apache.myfaces.custom.calendar.HtmlInputCalendar
I do not have an intimate knowledge of JSF innerds yet so if somebody could help me out I would be much appreciative. Basically I am just looking for a way to update a <h:inputCalendar> field after the initial page load. I have tried using the binding attribute thinking I might have some additional control from that avenue, but it still only calls the getter property on the initial page load and not subsequent page loads.
Thanks in advance, Aaron Bartell http://mowyourlawn.com
On 5/9/05, Aaron Bartell <[EMAIL PROTECTED]> wrote:
After reading the documentation for inputDate
(http://myfaces.apache.org/tlddoc/) I found that the
'value' attribute is only used for the initial value when the component is
rendered for the first time. Why is this so? I have a need to change the
date programmatically based on another field changing on the screen (coupled
with a post back to server) but the way this component is set to work makes
it so it can't be set to a different value.
Any comments?
Thanks,
Aaron Bartell
