I had a similar problem in the last few days, and someone pointed me to
this wiki page (which has some alternative solutions compared to the
link you posted) [1]
As for why...?
[1] http://wiki.apache.org/myfaces/ClearInputComponents
David Boyd wrote:
:) I know how the component works assuming he just queues the
valueChangedEvent
I have blogged alternate solutions as well
http://java-server-faces.blogspot.com/2006/04/valuechangelisteners-what-
you-need-to.html
but what I want to know is why?
Why does this happen is it a bug? An error in the specification etc?
Why does it update for output components and not for input components?
:)
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Matthias Wessendorf
Sent: Wednesday, June 14, 2006 3:19 PM
To: MyFaces Discussion
Subject: [SPAM] Re: Re: inputText not updating from valueChangedListener
b=uiHnFQ/OI6ffgtiEOG3tJasR/b3KIloGE0HVZIA/gXjDXV5uj+brPkcfAA1+oua/vOI4od
r6PVJv/WBc9KI6BmuIpaX89n48F32n/eWZylcJ6jCZ3joEMg1XLwoFt0CH5NV3gbN2tbhjly
fvLRq38xG16WMYpPTuTxQSvd/eCkE= b=e8e1XF
that guy deliveres the event later. (custom event)
Regards,
Matthias
On 6/13/06, David Boyd <[EMAIL PROTECTED]> wrote:
But then you have the problem where the setter methods are called
after
valueChanged code
i.e
Any variables in your beans you change in your valueChanged methods
will
be overwritten by your setter methods
This is a common problem
Just check out
http://www.irian.at/myfaces-sandbox/valueChangeNotifier.jsf
There is even a component to overcome the deficiencies in value
Changed
methods
I am more curious to know why this happens? I have a found solutions
to
fix this problem e.g sandbox valueChangeNoifier
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
Matthias Wessendorf
Sent: Wednesday, June 14, 2006 2:50 PM
To: MyFaces Discussion
Subject: [SPAM] Re: inputText not updating from valueChangedListener
b=uiHnFQ/OI6ffgtiEOG3tJasR/b3KIloGE0HVZIA/gXjDXV5uj+brPkcfAA1+oua/vOI4od
r6PVJv/WBc9KI6BmuIpaX89n48F32n/eWZylcJ6jCZ3joEMg1XLwoFt0CH5NV3gbN2tbhjly
fvLRq38xG16WMYpPTuTxQSvd/eCkE=
have you tried without responsecomplete() ?
On 6/13/06, David Boyd <[EMAIL PROTECTED]> wrote:
Hey all,
I know this problem most likely would have been addressed before but
was
just wondering if there has been any solution for it?
Say you had
<t:selectOneMenu value="#{bean.test}"
onchange="submit();"
valueChangeListener="#{bean.changedMethod}">
<f:selectItem itemValue="a" itemLabel="a"/>
<f:selectItem itemValue="b" itemLabel="b"/>
</t:selectOneMenu>
<t:inputText value="#{bean.userName}" />
<t:outputText " value="#{bean.userName}" />
and you have the value change method
private userName;
//getters and setters for userName
public void changedMethod(ValueChangeEvent event)
{
userName = "someValue";
FacesContext.getCurrentInstance().renderResponse();
}
Just wondering why does the outputText update but the inputText does
not?
i.e why does the outputText display "someValue" and the inputText is
still
empty?
I know if you bind the inputText and call the setSubmittedValue()
you
can
update the inputText
Just wondering if I can get an explanation of why this problem
occurs?
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
